The Data Object Broker handles the coordination and management of data. It updates and provides data integrity for the MetaStor and acts as a server to the Execution Environment. It also performs data accesses and updates on behalf of a transaction running in a session.
The MetaStor is an active store for all TIBCO Object Service Broker metadata: definitions, characteristics, access paths, and storage locations of all objects (data and programs) in a node with its own MetaStor. Every Data Object Broker has its own MetaStor. A node is the name associated with a Data Object Broker. In a distributed environment the node name is used to identify a Data Object Broker to another Data Object Broker.
TIBCO Object Service Broker for z/OS Installing and Operating,
TIBCO Object Service Broker for Open Systems Installing and Operating, and
TIBCO Object Service Broker Application Administration about the Data Object Broker, nodes, and distributed environments.
The Execution Environment is the component of TIBCO Object Service Broker that interacts with the end user or TIBCO Object Service Broker application. It uses a rules language to manage tasks such as presentation, command interpretation, and logical data control. The Execution Environment runs applications written in rules for the user and communicates with a Data Object Broker on behalf of the user.
The rules language is a very simple programming language used to develop TIBCO Object Service Broker applications. The following lists a few of its characteristics:
TIBCO Object Service Broker Programming in Rules for details about the rules language and rules programming.
TIBCO Object Service Broker for z/OS External Environments about the available z/OS programmable interfaces and how to use them.
TIBCO Object Service Broker for Open Systems External Environments about the available programmable interfaces for the Windows and Solaris platforms and how to use them.
The client services layer provides the interface between TIBCO Object Service Broker and its host operating environment. Depending on the client interface, users are provided with either an application program interface or a workbench of TIBCO Object Service Broker tools. The following table describes the client interfaces that you can use to access TIBCO Object Service Broker:
|
Data Object Broker Platform
|
|
|
|
|
Application Programming Interface (API) that connects TIBCO Object Service Broker and client programs written in Java.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TIBCO Object Service Broker for z/OS External Environments about the available z/OS programmable interfaces and how to use them.
TIBCO Object Service Broker for Open Systems External Environments about the available programmable interfaces for Open Systems and how to use them.