Encapsulate an Application

---

In this example, information flow between the applications is already automated by means of custom database maps. But you would like to be able to modify one of the applications without disrupting the entire landscape of applications. One way to do this is to map the output of upstream applications, and the input of the target application to ISO 15926-4.

Error: Macro Image(GettingStarted_Encapsulate01.JPG, 400px) failed

Attachment 'wiki:ISO15926Primer_GettingStarted_Encapsulate: GettingStarted_Encapsulate01.JPG' does not exist.

Figure 1 - Hard-Coded Custom Maps

This is called Encapsulating. The application using the 15926-4 dictionary. After you do this, the application can be modified, or changed out entirely, as long as the inputs are still mapped to 15926-4

Error: Macro Image(GettingStarted_Encapsulate02.JPG, 400px) failed

Attachment 'wiki:ISO15926Primer_GettingStarted_Encapsulate: GettingStarted_Encapsulate02.JPG' does not exist.

Figure 2 - Encapsulate an Application

Next

• Primer: Decouple an Application from a Confederation of Applications

---