Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 1 About the TIBCO Object Service Broker System : About TIBCO Object Service Broker Architecture

About TIBCO Object Service Broker Architecture
TIBCO Object Service Broker is a transactional processing environment consisting of an application development interface, a code execution environment, and a physical database.
These entities can all exist on one physical machine or they can be distributed across different machines. The following diagram illustrates this relationship:
Client Services Layer
The client services layer provides the interface between TIBCO Object Service Broker and its host operating environment, referred to as an external environment in this manual. This layer provides support for TIBCO Object Service Broker sessions running under, for example, SDK (C/C++), SDK (Java), Object Integration Gateway, Telnet 3270, or external routines. Every TIBCO Object Service Broker session that runs in an Execution Environment is started by a client.
Execution Environment
The Execution Environment manages sessions where you execute TIBCO Object Service Broker rules and access TIBCO Object Service Broker tables. The Execution Environment has two parts: the TIBCO Object Service Broker monitor (osMon) process and the osee program.
The osMon process creates, manages, and terminates sessions. It establishes links with entities outside the Execution Environment. You must run osMon before starting a TIBCO Object Service Broker session and should terminate it only after all sessions are done. When you request the start of a TIBCO Object Service Broker session, osMon creates an osee as necessary for your use. The osee program delegates actions to a session it has created and supervises the session while it exists. Execution Environments are either single- or multiple-session.
More than one Execution Environment can reside on one machine, and multiple Execution Environments can interact with the same Data Objext Broker. Although one session can interact with only one Data Object Broker directly, it can interact with other Data Object Brokers through distributed data access between Data Object Brokers.
Data Object Broker
The Data Object Broker handles the co-ordination and management of transactional table data. It acts as the transactional commit coordinator, and in this capacity manages the integrity of transactional data. It can also route data access traffic to another Data Object Broker or to an external database server. The logical view of the data that it manages is kept in the MetaStor.
Physical Data Store
The physical data store, known as the Pagestore, is where the actual data is stored on a physical device in a device dependent format. TIBCO Object Service Broker makes use of this device dependent format to store its logical, relational table view of data.
External Database Servers
External database servers allow TIBCO Object Service Broker to access other types of data on external databases. For detailed information about external database servers, refer to the TIBCO Service Gateway manual that accompanies each external database server.
See Also
TIBCO Object Service Broker for Open Systems Installing and Operating for information about configuration setup.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved