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


Chapter 1 TIBCO Object Service Broker Concepts : TIBCO Object Service Broker Components

TIBCO Object Service Broker Components
These are the main components of an TIBCO Object Service Broker system:
Primary Components Illustrated
The following diagram illustrates the primary components of TIBCO Object Service Broker:
Data Object Broker
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.
 
MetaStor
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.
See Also
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.
Execution Environment
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.
Rules Language
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:
A simple tutorial illustrating how to write applications using the rules language is available in Chapter 3, A Quick TIBCO Object Service Broker Tutorial.
See Also
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.
Client Interfaces
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
User Interface
SDK (Java)
Application Programming Interface (API) that connects TIBCO Object Service Broker and client programs written in Java.
SDK (C/C++)
API that connects TIBCO Object Service Broker and client programs written in third-generation languages, such as C.
TIBCO Object Service Broker UI
Program with a graphical user interface that you use to develop applications.
Open Systems
Program that starts a TIBCO Object Service Broker workbench in a text format.
Open Systems
Terminal protocol by which TIBCO Object Service Broker can be accessed.
Open Systems
Program that starts TIBCO Object Service Broker as a batch process.
Program that starts TIBCO Object Service Broker workbench as a TSO process.
Set of programs that start a TIBCO Object Service Broker workbench as a CICS process.
Set of programs that start a TIBCO Object Service Broker workbench as an IMS TM process.
Call Level Interface
API that connects TIBCO Object Service Broker and client programs written in third-generation languages, such as COBOL or assembler.
Program that starts TIBCO Object Service Broker as a batch process.
Connectivity that enables TIBCO Object Service Broker to run as a VTAM application.

1
Requires the Service Gateway for CICS, which is a separately purchased component.

2
Requires the Service Gateway for IMS TM, which is a separately purchased component.

See Also
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.

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