| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:TaskDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="-QqiIwonwt-ErT139DDUqsA" |
| name="design_reference_data_integration,_HMQasGDFEdyKlZvvtnMrMg" guid="-QqiIwonwt-ErT139DDUqsA" |
| authors="Jerome Boyer" changeDate="2008-09-24T13:26:10.530-0700"> |
| <mainDescription><p>
 |
| From the methodology point of view data management need to be looked into: data origination, data management, and data
 |
| consumption. The architect needs to understand how the master data are coming from and how they are updated. The life
 |
| cycle of such data can lead to version and management control, that may add complexity on top of the services
 |
| versioning. The data consumption has to be addressed for the execution environment and also in the case of BRMS
 |
| deployment for the rule authoring environment.
 |
| </p>
 |
| <p>
 |
| The following diagram highlights a high level architecture&nbsp;architect can leverage to design&nbsp;his own solution.
 |
| </p><br />
 |
| <p>
 |
| <img height="499" alt="" src="resources/MDM.bmp" width="557" /><br />
 |
| </p>
 |
| <p>
 |
| The master data are centralized in a repository, and technology as Master Data Management product can be&nbsp;used for
 |
| that. The different sources of data are synchronized with this repository on a regular basis, using different
 |
| implementation mechanism based on ETL, ESB, web services or custom layer. A mapping mechanism&nbsp;as to be applied to
 |
| persist the data in the repository. The Execution environment can fetch the last version or a given version of the data
 |
| from this repository and cache it.
 |
| </p>
 |
| <p>
 |
| The same applies for the rule authoring environment: The&nbsp;BRMS server can load the data and cache it in the web
 |
| server. With such simple architecture the rule writer can have access to a unique definition of the enumerated domains
 |
| or other business objects, like a Product definition.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:TaskDescription> |
