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


Chapter 2 Configuring the Data Object Broker : Data Object Broker Special Files

Data Object Broker Special Files
What are the Special Files?
The following files are known collectively as the Data Object Broker special files:
These files are located in the install_path/database directory (install_path is set with the HURON environment variable), and have the following default names:
Description and Size of the Special Files
MetaStor
The MetaStor, a symbolic name for segment 0, is the active store for all TIBCO Object Service Broker metadata. It maintains the definitions, characteristics, access paths, and storage locations of all objects in TIBCO Object Service Broker. Every Data Object Broker has its own MetaStor.
The MetaStor must contain at least 27,000 pages (three 9000 4 KB pages, the default). Most of this space is occupied by the unloaded MetaStor image that is part of the TIBCO Object Service Broker distribution. TIBCO Object Service Broker rules, screens, reports, and table definitions that users create are also kept in the MetaStor.
Segment 1
Segment 1 stores TIBCO Object Service Broker users’ table occurrences. It should occupy no less than 5,000 pages (the default). For larger TIBCO Object Service Broker systems, segment 1 could occupy tens or hundreds of thousands of pages, and like any other segment, can be divided into two or more page data files. You can have other segments defined (for example, segment 2, segment 3, and others); the default database definition file install_path/database/dbdef defines only the MetaStor, segment 1, and segment 99.
Journals
TIBCO Object Service Broker contains two journals, which perform the following tasks:
When the system performs a checkpoint, all modified data pages in the resident page manager buffers are copied to the cache portion of the journal, therefore assuring their recoverability in the event of a failure. The resident page manager is an internal Data Object Broker component that manages local memory containing images of all Pagestore pages currently in use.
The system switches between journals when one reaches capacity and the contents of the full journal are saved. The procedure to save the full journal is called a spin. The journals can be placed on the same SCSI controller as the redolog, but they must be in a different directory.
Contingency Log
The contingency log contains a record of every in-doubt or contingent transaction.
Redolog
The redolog contains records of all update operations recently performed, or about to be performed, against the database. TIBCO Object Service Broker uses the redolog to reconstruct the committed updates made between checkpoints and maintain database integrity.
The redolog file should be defined at the head of a SCSI controller that is a different controller than the one containing the Pagestore page files.
Audit Log
The audit log records access to TIBCO Object Service Broker and its objects.
The full installation process initially places the audit log in the MetaStor (segment 0).
The size of the audit log depends on the level of logging that you set for the Execution Environment via the SECAUDITLOG Execution Environment parameter. This parameter can be set to STRICT, NORMAL, or DISABLED. STRICT causes logging of all accesses to objects with the Log Accesses flag set to Y in the Security Manager.
Because of the possible very large size of the log file, the audit log must be located in its own segment.
Use the hrnbrial utility to move the audit log, if you want to move it. The hrnbrial utility does not move the audit log segment if it was already moved once.
See Also
TIBCO Object Service Broker for Open Systems Managing Backup and Recovery for more information about journal processing and in-doubt and contingent transactions.
The hrnbrial utility in TIBCO Object Service Broker for Open Systems Utilities for information about moving the segment for the audit log.
TIBCO Object Service Broker Managing Security for more information about the audit log facility.
TIBCO Object Service Broker Parameters for more information about the SECAUDITLOG parameter.

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