Detecting and managing changes in business data integration solutions

• US 20080071844A1
• Filed: 09/15/2006
• Published: 03/20/2008
• Est. Priority Date: 09/15/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Ovanesyan, Oleg Gregory, Kapoor, Rahul, Cao, Peiwei, Manek, Parul, Gopal, Burra, Croicu, Alexandru, Annamalai, Muthiah K., Edelstein, Sharon E., Jain, Sandhya
• Granted Patent: US 7,987,159 B2
• Time in Patent Office: Days
• US Class Current: 707/204
• CPC Class Codes: G06F 16/254 Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses

Abstract

Methods, systems, and computer program products detect and manage changes in business data integration (BDI) solutions. BDI solutions include extracting, mapping, or loading source information from disparate sources as targets presented to business applications that consume targets. A method involves detecting changes in a BDI solution, classifying each of the changes based on change severity, analyzing what objects would be impacted by the changes, determining whether the objects impacted by the changes can be change handled without user intervention, and change handling without user intervention all the objects impacted by changes that are not severe. Still further, the method involves committing changes to a metadata repository and creating a deployable checkpoint of the metadata repository where the deployable checkpoint is consistent for all the changes handled in the BDI solution. The modularized metadata describes an end-to-end information flow and underlying dependencies between the source information, mappings, targets and business applications.

Claims

1. A method for detecting and managing changes in a business data integration (BDI) solution, comprising:

detecting one or more changes in a BDI solution wherein the BDI solution comprises extracting, mapping, or loading source information from disparate sources as one or more targets presented to one or more source-independent business applications that consume the targets;

classifying each of the changes based on change severity;

analyzing what objects would be impacted by the changes;

determining whether the objects impacted by the changes can be change handled without user intervention;

change handling without user intervention all the objects impacted by changes that are not severe;

committing the changes to a metadata repository; and

creating a deployable checkpoint of the metadata repository wherein the deployable checkpoint is consistent for all the changes handled in the BDI solution;

wherein modularized metadata stored in the metadata repository describes an end to end information flow and underlying dependencies between the source information, mappings, the targets and the source-independent business applications.

2. The method of claim 1, further comprising regenerating integration services packages for the objects comprising the targets changed in the BDI solution.

3. The method of claim 2, further comprising prior to committing the changes:

displaying all the changes wherein the changes are organized by at least one of the following;

business area, object type, or change type;

launching a user interface for each change handler associated with a change wherein the user interface is de-coupled from any logic that generates the integration services packages;

receiving a selection of a change from the user; and

updating a state of the BDI solution to reflect changes that have been handled and changes yet to be handled.

4. The method of claim 3, wherein displaying all the changes futher comprises at least one of the following:

displaying whether a corrective action associated with the change type has been taken;

when the corrective action has been taken, displaying the corrective action; and

displaying what corrective actions can be taken based on the change type or the object type.

5. The method of claim 3, further comprising:

identifying actions that can be taken for each grouping of impacted objects wherein the groupings of impacted objects may include groups of heterogeneous objects whereby a change to an impacted object at one end of the end-to-end information flow can trigger a change to a heterogeneous object at a second end of the end-to-end information flow.

6. The method of claim 5, wherein the groups of heterogeneous objects include at least two of the following:

packets, tables, mappings, files, views, stored procedures, web services, target information, connection information, transformation information, and references to information at least one of within or outside the metadata repository.

7. The method of claim 5, wherein the change to the impacted object triggers at least one of the following:

a change to a heterogeneous object in one or more of the business applications; and

a change to a heterogeneous object in one or more of the disparate sources of the source information.

8. The method of claim 1, further comprising:

browsing existing line of business (LOB) source systems;

discovering metadata of LOB source system objects that are needed for the BDI solution; and

comparing the metadata of objects in the LOB source systems with assumed definitions of objects in the metadata repository, wherein the assumed definitions are at least one of the following;

discovered from a same LOB source system; and

authored as pre-defined content of the metadata and installed as part of setting up the LOB source systems for a first time;

wherein detecting the changes comprises detecting changes in the metadata of objects in the LOB source systems.

9. The method of claim 1, further comprising receiving target schema definitions wherein the target schema definitions are authored by a user of the BDI solution or imported from another source system and wherein detecting the changes comprises detecting changes in the target schema definitions.

10. The method of claim, further comprising modifying mapping between the source information and the targets therein changing a linkage between the source system and a target system and requiring the changes to be managed and validated wherein detecting the changes comprises detecting modifications to the mapping.

11. A computer program product comprising a computer-readable medium having control logic stored therein for causing a computer to detect and manage changes in a business data integration (BDI) solution, the control logic comprising computer-readable program code for causing the computer to:

detectone or more changes in a BDI solution;

classify each of the changes based on change severity;

analyze what objects are impacted by the changes;

determine whether the objects impacted by the changes can be change handled without user intervention; and

change handling without user intervention all objects impacted by changes that are not severe.

12. The computer program product of claim 11, further comprising computer-readable program code for causing the computer to:

commit the changes to a metadata repository;

create a deployable checkpoint of the metadata repository; and

regenerate in bulk, integration services packages for the objects comprising targets changed in the BDI solution;

wherein metadata stored in the metadata repository describes an end to end information flow and underlying dependencies between source information, mappings, the targets and source-independent business applications.

13. The computer program product of claim 11, further comprising computer-readable program code for causing the computer prior to committing the changes to:

display all the changes wherein the changes are organized by at least one of the following;

business area, object type, or change type;

launch a user interface for each change handler associated with a change;

receive a selection of a change; and

update a state of the BDI solution to reflect changes that have been handled and changes yet to be handled.

14. The computer program product of claim 12, further comprising computer-readable program code for causing the computer to:

identify actions that can be taken for each grouping of impacted objects wherein the groupings of impacted objects may include groups of heterogeneous objects whereby a change to an impacted object at one end of the end-to-end information flow can trigger a change to a heterogeneous object at a second end of the end-to-end information flow.

15. The computer program product of claim 14, wherein the groups of heterogeneous objects include at least two of the following:

packets, tables, mappings, files, views, stored procedures, web services, target information, connection information, transformation information, and references to information at least one of within or outside the metadata repository.

16. The computer program product of claim 14, wherein the change to the impacted object triggers at least one of the following:

a change to a heterogeneous object in one or more of the business applications; and

a change to a heterogeneous object in one or more disparate sources of the source information.

17. The computer program product of claim 12, wherein the deployable checkpoint is consistent for all the changes handled in the BDI solution.

18. A system for managing changes detected in a business data integration (BDI) solution, the system comprising:

a data integration server operative to;

classify each of the changes based on change severity;

analyze what objects are impacted by the changes;

at least one client computer including a display in communication with the data integration server and operative to;

display all the changes wherein the changes are organized by at least one of the following;

business area, object type, or change type;

launch a user interface for each change handler associated with a change;

receive a selection of a change to handle; and

update a state of the BDI solution to reflect changes that have been handled and changes yet to be handled.

19. The system of claim 18, wherein the data integration server is further operative to:

determine whether the objects impacted by the changes can be change handled without user intervention;

change handling without user intervention all objects impacted by changes that are not severe.

commit the changes to a metadata repository;

create a deployable checkpoint of the metadata repository; and

regenerate integration services packages for the objects comprising targets changed in the BDI solution;

wherein metadata stored in the metadata repository describes an end to end information flow and underlying dependencies between source information, mappings, the targets and source-independent business applications.

20. The system of claim 19, wherein the data integration server is further operative to identify actions that can be taken for each grouping of impacted objects wherein the groupings of impacted objects may include groups of heterogeneous objects whereby a change to an impacted object at one end of the end-to-end information flow can trigger a change to a heterogeneous object at a second end of the end-to-end information flow.