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


Chapter 2 Configuring the Data Object Broker : Data Object Broker Directory File (huron.dir)

Data Object Broker Directory File (huron.dir)
You use the Data Object Broker directory file, huron.dir, to relate Data Object Broker names to the physical machines where they reside by defining the necessary IPC and TCP/IP communication attributes for TIBCO Object Service Broker systems. The Data Object Broker directory file is organized as a series of records that you can modify using a text editor.
To define a TIBCO Object Service Broker system for an Execution Engine, File Gateway, or another TIBCO Object Service Broker system (peer) to connect to it, just add another record to the Data Object Broker directory file. Detailed communication attributes do not have to be remembered when they are added to the Data Object Broker directory file.
Name and Placement of the Directory File
The Data Object Broker directory file path and name defaults to the value of the HURONDIR environment variable, which at installation is set to install_path/database/huron.dir. Ensure that the huron.dir file is:
Also ensure that the environment variable HURONDIR is set on all Data Object Broker and Execution Environment and File Gateway server machines.
What the Communication Attributes Define
The attributes in the Data Object Broker directory file define the communication resources needed by each TIBCO Object Service Broker system when:
Passing messages between TIBCO Object Service Broker components—clients processes, Execution Environments, external database servers—and their assigned Data Object Broker.
Data Object Broker communications uses System V shared memory and semaphore IPC resources when the components and Data Object Broker are on the same machine. It uses TCP/IP when the components and the Data Object Broker are on different machines.
Optionally, passing messages between peer TIBCO Object Service Broker systems through peer-to-peer distributed data connections using TCP/IP for communications.
Attributes Defined
Each record in the huron.dir file defines a set of communication attributes for one Data Object Broker. These attributes are used by components that must communicate with the Data Object Broker such as client processes, Execution Environments, external database servers, and peer Data Object Brokers:
 
Each record begins with the word node followed by a series of keyword attributes.
The communications identifier that identifies the Data Object Broker to connect to. If the value is greater than eight characters an alias attribute must be defined in the huron.dir file.
On Windows and Solaris, this value is specified by the NODENAME Data Object Broker parameter. On z/OS, this value is specified by the COMMID Data Object Broker parameter.
If name exceeds eight characters, an alias of up to eight characters must be specified; if the name is eight characters or fewer, alias is optional. If specified, the alias is used as the communications identifier for communications among the z/OS, Windows, and Solaris, environments.
The machine where the Data Object Broker operates can be specified as either an IPV4 or IPV6 address or as a fully qualified symbolic host name (for example, host=machine.world.com). For host names, the system hosts file is used to resolve the name to an IP address).
The TCP/IP address of the host. Specified using IPV4 or IPV6 format. This should be used only if the host name is not defined to TCP/IP.
A four-digit number greater than 1024 that is unique for each Data Object Broker. The port is used by TCP/IP and must be unique within each machine for all applications using TCP/IP. Using port numbers greater than 10000 usually ensures that Data Object Broker port numbers do not conflict with other applications.
This optional value enables TCP/IP keepalive probes which will facilitate the detection of severed, idle connections, as well as possibly preventing the severing of idle connections by firewalls. On platforms that do not support a TCP/IP keepalive feature, the functionality is emulated with periodic out-of-band messages between TIBCO Object Service Broker components. The value is an integer between 1 and 65535, which specifies the interval in seconds between probes on outbound connections to this node.
A three-byte hexadecimal number (0x1 through 0xffffff) that identifies shared memory and semaphores (IPC resources) for each Data Object Broker. Each Data Object Broker must have a unique IPC key within each machine. Its value cannot be 0.
For Windows only. Specify a timeout value in milliseconds. The range of allowed values is 0 to 2,147,483,647 milliseconds. The default value of 0 represents an infinite timeout period.
This parameter specifies the amount of time a peer or peer server waits for a message before giving up. With the use of this parameter, communication failures can be detected when communications are lost in a non-controlled way, because of the use of a KEEPALIVE type of functionality. Peers can then be reconnected automatically when the client site comes back up, after the communications network fails, or after the site of a connected client fails, such as during a power outage. Such failures previously required shutting down the server Data Object Broker and restarting it.
For TCP/IP, you should use a value of 60000 and adjust the value depending on observed behavior of the system. If the value is too small, peers could constantly be starting and stopping, while a value that is too large can cause delays in sensing an outage and beginning corrective action. No special conditions are raised when a timeout successfully recovers a connection.
For TCP/IP, the timeout is a property of the local node. If the local node services an incoming z/OS remote peer, the timeout value should be set to 0 to disable the timeout processing.
Sample huron.dir File
node name=acamar,
host=acamar.world.com,
port=8000,
ipckey=0x8000
node name=kabul,
host=crocus.world.com,
port=8001,
ipckey=0x8001
node name=niagara,
host=niagara.world.com,
port=8002,
ipckey=0x8002

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