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


Chapter 2 Configuring the Data Object Broker : Processes That Form the Data Object Broker

Processes That Form the Data Object Broker
Starting the Data Object Broker activates TIBCO Object Service Broker. The Data Object Broker operates as a set of processes that work closely together to give the appearance of a single entity. It is started and controlled using the hrncr command. The specific processes that are started and the number of processes that are started depend on the Data Object Broker configuration parameters, set in the crparm file in the install_path/database directory.
Refer to TIBCO Object Service Broker Operator Commands for more information about the hrncr command and to Setting Data Object Broker Parameters for more information about the crparm file.
Description of Processes
The processes that form the Data Object Broker are:
 
Supervisor that starts other processes, times events, handles shutdown and abnormal termination, and provides information about the release level of TIBCO Object Service Broker and the state of the Data Object Broker.
Database application that contains TDS and distributed data support. The number of hrnappl processes started is determined by the MAXCONCURRENT Data Object Broker parameter.
Process that acts as an outage notification daemon for IPC communications. This process forwards a disconnection message to the work queue serviced by the hrnappl processes on behalf of an abnormally terminating local client.
A checkpoint is created if the redolog is 50% full or the resident page manager buffers are 15% full.
Redolog and contingency log manager, which handles transaction commit integrity and distributed data integrity. It also handles transaction recovery if the Data Object Broker is started after an abnormal termination or system outage.
Process that handles outbound connections via TCP/IP. An hrncomm process is started for every outbound connection made (that is, one process for each thread). Currently, connections are made only to peer Data Object Brokers. If there are no PEERS parameters specified in the Data Object Broker parameter file then no hrncomm process is started. Refer to Chapter 5, Configuring a Communication Environment for Access of Distributed Data for more information about communications to peer Data Object Brokers.
Process that handles inbound connections to this Data Object Broker via TCP/IP. The hrncomt process is a listening process.
See Also
TIBCO Object Service Broker for Open Systems Managing Backup and Recovery for information about checkpoint processing.
TIBCO Object Service Broker Parameters for more information about parameters.

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