Architecture

The figure below illustrates the architecture of Business Object Processing Framework (BOPF), which is separated into the principal areas explained below:

• Consumer

  The consumer uses core services provided by the transaction layer to access business object instances and to control transactions. Usually, the consumer is implemented as a user interface or an autonomous process participant.

• Transaction Layer

  The transaction layer consists of a central transaction manager instance that allows the consumer to save all changed business object instances of the current transaction. In addition, a service manager instance for each business object provides core services to access all business object instances of each business object. For example, using the RETRIEVE core service the consumer can read data from business object instances.

• BOPF Model

  At design time, each modeled business object consists of several entities. You can maintain the model information in Business Object Builder (BO Builder). The Business Object runtime (BO runtime) uses the information. For example, if a specific business object consists of an action entity, the name of the action's implementing class is stored in the business object model.

• BO Runtime & Application

  The BO runtime executes the requested core services and therefore instantiates and invokes the application (implementing classes of entities of a business object). For example, if the consumer calls the DO_ACTION core service, the BO runtime instantiates and invokes its implementing class and hands over the control to the implementation class. After the action has been executed, BOPF collects the result and returns it to the consumer.

• Buffer and Database

  To avoid redundant database accesses due to performance reasons, business objects autonomously buffer database accesses. Additionally, the buffer manages the transactional changes.