Copyright © Cloud Software Group, Inc. All Rights Reserved

Description of the Files

Data Object Broker Parameter Files

File Name

Either one of the following:

•	%OS_ROOT%\database\crparm (Windows)

•	${OS_ROOT}/database/crparm (Solaris)

Description

This file allows the TIBCO Object Service Broker administrator to tailor the operation of the Data Object Broker. Some of the parameters are used to handle operating system differences, others are used to set the expected work load and throughput, while still others control such functions as logging and tracing. Refer to TIBCO Object Service Broker Parameters for more information about Parameters.

Form

The parameters are all of the form:

PARAMETER=value

Usage Notes

•	Before changing the value of a parameter in this file, you must shut down the Data Object Broker.

•	Only one parameter is allowed on each line.

•	Blank lines and white space are ignored.

•	Comments begin with the number sign (#) character and continue to the end of the line.

•	The parameter names and values are not case sensitive.

Database Definition

File Name

Either one of the following:

•	%OS_ROOT%\database\dbdef (Windows)

•	${OS_ROOT}/database/dbdef (Solaris)

Description

This file is used to define the segments, journals, and logs that comprise the TIBCO Object Service Broker database. Primarily this means defining the name of each segment (and thereby the subdirectory) and the number of files in which the segment is stored.

Form

The dbdef file consists of two types of lines:

DB or main line

Defines properties and directory paths for default file locations. Each DB line contains one definition. Blank lines and white space are ignored. Comments begin with the # character and continue to the end of the line. The keyword names and values (except for the PATH and FILE values on the Solaris platform) are case insensitive. Each Data Object Broker special file is described by a single DB (or main) line in the dbdef file. Among other properties, the DB line can define the default path for all files that belong to the special file. The DB line uses the following syntax: DB TYPE=type,NAME=name[,ACBS=numfiles] [,ID=segno] [,INIT=initflag] [,PATH=pathstring]

FILE subcommand linde

Specifies the directory path to a file described in the preceding DB line, overriding the default path to the file. FILE lines are optional. The filename is determined by the NAME parameter in the DB line. The FILE line uses the following syntax: FILE FILENO=n [,PATH=pathstring]

Variable Descriptions

 

type	CLOG, JOURNAL, PAGE, or REDOLOG.
name	The name of the Data Object Broker special file. This is the name of the subdirectory (under database) that contains the segment, journal, or log files. The name is converted to uppercase.
numfiles	The number of separate files involved, depending on the value of TYPE and NAME, as shown here:
	TYPE=CLOG		ACBS=1
	TYPE=JOURNAL		ACBS=2
	TYPE=PAGE, NAME=METASTOR		ACBS=3
	TYPE=PAGE, NAME=AUDITLOG		ACBS=1
	TYPE=PAGE, NAME=PageFileName		ACBS=the number of page files associated with the segment, to a maximum of 128. This number depends on the number of disks available for the database (Solaris) or the actual number of page files required (Windows).
	TYPE=REDOLOG		ACBS=1
segno	The segment number, when TYPE=PAGE. The range of valid values is 0 (for the MetaStor) to 255.
initflag	When TYPE=PAGE, this determines if the segment should be online after Data Object Broker startup. Valid values are YES and NO. The alternative is to have the TIBCO Object Service Broker system administrator activate the segment explicitly using the dbonline operator command. The INIT value for a segment can be changed at any time, for the next restart of the Data Object Broker, except for segment 0, which must be available at all times.
path_string	The default (on the DB line) or the actual (on the FILE line) directory path for the segment or log.
n	Range from 1 to 128. This value cannot be greater than the ACBS value on the corresponding DB line.

Usage Notes

•	Only one definition is allowed on each line.

•	Blank lines and white space are ignored.

•	Comments begin with the hash (#) character and continue to the end of the line.

•	The keyword names and values (except for the PATH and FILE values on the Solaris platform) are case insensitive.

•	To increase the number of page files in your Pagestore, increase the ACBS value accordingly before formatting the new page files.

Example

DB    TYPE=PAGE,ACBS=4,NAME=METASTOR,INIT=YES

FILE  FILENO=1,PATH=D:\MetaStor1\

FILE  FILENO=2,PATH=D:\MetaStor2\

FILE  FILENO=3,PATH=D:\MetaStor3\

FILE  FILENO=4,PATH=D:\MetaStor4\

Data Object Broker Log File

File Name

Either one of the following:

•	%OS_ROOT%\log\hrncr.* (Windows)

•	${OS_ROOT}/log/hrncr.* (Solaris)

Description

This file is used to log Data Object Broker activity and problems. It is normally one of the first places to look if a problem involving the Data Object Broker is suspected.

Usage Notes

•	Every time the Data Object Broker is started it creates a log file in the log directory.

•	The name of this file is platform-dependent.

Windows	hrncr.nnn	nnn is an incrementally sequential counter that uniquely identifies the log file.
Solaris	hrncr.nnnnn	nnnnn is the process ID of the Data Object Broker supervisor—the background hrncr process.

TIBCO Object Service Broker Directory

File name

Either one of the following:

•	%OS_ROOT%\database\huron.dir (Windows)

•	${OS_ROOT}/database/huron.dir (Solaris)

Description

This file is used to define a list of TIBCO Object Service Broker nodes. The directory is used by TIBCO Object Service Broker Communication Support (OCS). By default the directory is located in %OS_ROOT%\database\huron.dir, but this location can be overridden by the HURONDIR environment variable. Refer to TIBCO Object Service Broker Parameters for more information about Parameters.

Form

Each entry has the following form:

NODE NAME=longname,

ALIAS=shortname,

HOST=hostname,

IP=ipaddress,

SERVICE=servicename,

PORT=portnumber,

IPCKEY=ipckey,

TIMEOUT=timeoutvalue

Variable Descriptions

 

longname	The full name of the node. 1 to 16 alphanumeric characters. Corresponds to the Data Object Broker NODENAME parameter. If longname is longer than eight characters, an ALIAS must also be specified.
shortname	A shortened version of the node name. 1 to 8 alphanumeric characters. Required if the node name is longer than eight characters.
hostname	The name of the TCP/IP host where the node resides. Use the fully qualified Internet host name, or the alias used within TCP/IP. Mandatory unless the node resides on z/OS.
ipaddress	The TCP/IP address of the host. Specified using decimal delimiters (for example, 126.0.0.56). This should be used only if the host name is not resolvable.
servicename	The service name used by this node for TCP/IP communication. 1 to 8 alphanumeric characters.
portnumber	The TCP/IP port where this Data Object Broker listens for incoming connections (should be 10000 or higher).
ipckey	Identifier used for semaphores and shared memory communications. Must not conflict with other Data Object Brokers running on the same system.
timeoutvalue	Optional timeout value specifying the timeout time for unresponsive outbound connections to a server. The range is 0 to 2,147,483,647 milliseconds. This parameter is implemented only for Windows; it is ignored in a Solaris environment. Note  Only for the hrncr (TIBCO Object Service Broker Data Object Broker) utility and the hrntladm (Administration Menu) utility

Usage Notes

•	All keywords and values can be specified in upper or lowercase—the data is not case sensitive.

•	An entry can be contained on one line or spread over several by ensuring that the last character on a line that is not whitespace is a comma.

•	Comments begin with the hash (#) character and continue to the end of the line.

Copyright © Cloud Software Group, Inc. All Rights Reserved