---

Object Store Coordinator

By default, an application has exactly one object store coordinator, as illustrated in “Figure 5-1.” An object store coordinator manages possibly many cooperating object stores (usually database contexts, each of which represents a data source), as “Figure 5-2” illustrates. This allows individual instances of enterprise objects to include data from multiple data sources and it allows enterprise objects constituted from data in different repositories to interact with one another.

In “Figure 5-2,” the object store coordinator manages the interactions between enterprise objects that need to communicate both with a MySQL database and an Oracle database. An object store coordinator is by default associated with as many database contexts (cooperating object stores) as the number of distinct data sources the application connects to.

So as illustrated in “Figure 5-2,” an application that uses two models, each model connecting to a different data source, has one object store coordinator that mediates between two separate cooperating object stores (database contexts). By default, each cooperating object store has its own database channel and its own adaptor channel.

The object store coordinator allows the application to use multiple data sources and also allows the application’s enterprise objects to consist of data from multiple data sources. The object store coordinator manages the logic that is necessary to support these features.

---