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


Chapter 1 Introduction : TIBCO Object Service Broker Architecture

TIBCO Object Service Broker Architecture
TIBCO Object Service Broker consists of three components:
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 as z/OS batch, TSO, CICS, IMS TM, or Native Execution Environment clients. Every TIBCO Object Service Broker session that runs in an Execution Environment is started by a client.
Execution Environment
The Execution Environment manages TIBCO Object Service Broker sessions, allowing you to execute rules and access tables and sessions. More than one Execution Environment can reside on a machine. An Execution Environment can reside on the same machine as a Data Object Broker or on a separate machine. Although the Execution Environment can interact with only one Data Object Broker directly, it can interact indirectly with other Data Object Brokers through distributed data access between Data Object Brokers.
The Execution Environment creates, manages, and terminates sessions. It establishes links with entities outside the Execution Environment. It delegates actions to a session once it is created and supervises the session while it exists.
The Execution Environment is established before any TIBCO Object Service Broker session is started and terminated after all sessions are done. Execution Environments are either single- or multiple-session.
TIBCO Object Service Broker Sessions
Within a session there can be one or more data access transactions. The session provides the context within which transactions can manipulate data and request access to relational data. Within this context:
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.

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