The Object Broker models (OBJECT-CLIENT-SUBPROGRAM, OBJECT-SERVER-SUBPROGRAM, OBJECT-DISPATCHER-SUBPROGRAM) are used together to generate an object maintenance program that runs on a Client-Server architecture.
These models are based on the Construct Object Models, that separate the maintenance of an object in two different components: the Access layer and the Presentation layer. In a Construct Object Structure all the Data Access is encapsulated in an Object Subprogram (Access layer), while the user interface is implemented with the Object Maintenance Dialog (Presentation layer).
Construct Object Models
By using the new set of models it is possible to open existing systems to external applications. The Object Broker Models will automatically generate all the codes that allow to run the dialog component of a maintenance structure on one platform, and the access component on a different machine.
Let's call CLIENT-COMPONENT the environment where a customer can submit a specific request, and SERVER-COMPONENT the environment where the data to be accessed resides. Client Component and Server Component can be located on the same machine or on different machines running (Entire Network). The requests between Client Component and Server Component use the middleware component ENTIRE BROKER.
With these models the OBJECT-DIALOG-PROGRAM exchange messages with the OBJECT-CLIENT-SUBPROGRAM (instead of the OBJECT-CLIENT-SUBPROGRAM). The OBJECT-CLIENT-SUBPROGRAM will issue a Broker request to a SERVER that manages the communication with the actual OBJECT-SUBPROGRAM.
The SERVER-COMPONENT can be implemented in 2 alternative ways:
Object Broker Models with Dedicated Server
Object Broker Models with Shared Server