Databases Reference
In-Depth Information
System
System
System
System
APPLICATIVE EVENT
ESB
MDM
ESB Configuration
Data approval
process
CCU
CCU
CCU
CCU
CCU
ORGANIZATIONAL EVENT
Business object's lifecycle
Return To Sender (RTS)
[undeliverable]
Undeliverable as Addressed
Insufficient Address
No such number
[insufficient]
[no such number]
BUSINESS EVENT
archive/archive()
start/start()
check/check()
[ok]
archive/archive()
T o be checked
Valid
Archive
check/check()
remove/remove()
[not complete]
To be completed
CCU
Use case
comp let e/comp lete()
Figure 12.6.
The synchronization of the MDM with the rest of the system
Indeed, a third level of synchronization exists that
intervenes when the states of business objects evolve. For
example, during the updates of the characteristics of the
“Product” business object in the MDM system, we might
want to synchronize the data with other systems only when
the product state changes from “to be negotiated” to the
“negotiated” state. This new synchronization possibility
dramatically changes the way in which the MDM system is
synchronized.
Instead of a static repository that must notify the ESB of
each of the data modifications, we have a more dynamic
MDM system that benefits from the lifecycles of business
objects to optimize its relationship with the ESB. Of course,
in order to achieve this, it is necessary to implement the
maturity level of the “semantic MDM” with a complete
modeling of data that is not limited to a static description
4
.
4
. See the state machine example of the business object “Address”
described in Chapter 9.
