OZ is configured using the "mama.properties" file, as described in the OpenMAMA Developer's Guide.
In the following examples, settings are prefixed by "mama.zmq.transport.{name}.", where "{name}" is the name of the transport, as specified in mamaTransport_create.
| Parameter | Default Value | Description |
|---|---|---|
| type | tcp | OZ currently supports only tcp. Any other value is silently ignored. |
| publish_address | lo | Specifies the interface the transport should use to publish messages. Applies to both naming and data sockets. |
| socket_monitor | 1 | Specifies whether to enable monitoring of socket connects/disconnects. When active, socket activity will be logged to stderr. For more information, see Monitoring Socket Events. |
| is_naming | 1 | Specifies that the transport is a "naming" transport. For more information, see Naming Service/Peer Discovery. |
| heartbeat_interval | 10 | Specifies the heartbeat interval for client (connecting) sockets, both naming and data. The code calls zmq_setsockopt(..., ZMQ_HEARTBEAT_IVL with this value (* 1000). |
| reconnect_interval | 10 | Specifies the reconnect interval for client (connecting) sockets, both naming and data. The code calls zmq_setsockopt(..., ZMQ_RECONNECT_IVL with this value (* 1000). |
| reconnect_stop | 0x1 | Specifies the reconnect option for client (connecting) sockets, both naming and data. The code calls zmq_setsockopt(..., ZMQ_RECONNECT_STOP with this value. Note that the values are listed in zmq.h, and can be ORed together. |
| log_level_naming | 4 (MAMA_LOG_LEVEL_NORMAL) |
Specifies the Mama logging level to use for naming messages. |
| log_level_beacon | 5 (MAMA_LOG_LEVEL_FINER) |
Specifies the Mama logging level to use for beacon messages, which is a special kind of naming message. If beaconing is enabled, there will be a LOT of these. |
| log_level_inbox | 5 (MAMA_LOG_LEVEL_FINER) |
Specifies the Mama logging level to use for inbox messages. You would typically not want/need to see these messages, but it's possible to enable them for troubleshooting/debugging purposes. |
The following settings apply only to "naming" transports (i.e., transports that use an nsd/proxy connection to discover peers).
| Parameter | Default Value | Description |
|---|---|---|
| naming.subscribe_address_0 | 127.0.0.1 | Specifies the address of an nsd/proxy process to connect to. |
| naming.subscribe_port_0 | 5756 | Specifies the port at which to connect to the nsd/proxy process specified in subscribe_address_0. |
| naming.subscribe_address_1, naming.subscribe_address_2 | Similar to subscribe_address_0, except no default value. |
|
| naming.subscribe_port_1, naming.subscribe_port_2 | Similar to subscribe_port_0 , except no default value. |
|
| naming.wait_for_connect | 1 | Specifies that the transport should block until it receives at least one "welcome" message from nsd/proxy. The transport will make connect_retries attempts, waiting connect_interval seconds after each attempt. If the transport has still not received a welcome message, it will terminate with an error. |
| naming.connect_retries | 100 | |
| naming.connect_interval | .1 | |
| naming.retry_connects | 1 | Whether to retry connects on the naming sockets. Note that this does not apply to the initial connection (see connect_retries above for that), but rather in the case where an established nsd/proxy connection has been disconnected. This is implemented in the transport by calling zmq_setsockopt(..., ZMQ_RECONNECT_IVL) with the value of retry_interval. |
| naming.retry_interval | 10 | |
| naming.beacon_interval | 1 | Specifies how often to publish "beacon" (announcement) messages. If set to zero, no beacons will be sent. Cannot be less than .1 (100 ms). |
The following settings apply to "data" sockets, in both naming and non-naming modes.
The following settings apply to data sockets, but only in non-naming mode.
| Parameter | Default Value | Description |
|---|---|---|
| incoming_url, incoming_url_1 .. incoming_url_256 | Specifies endpoint addresses that should be used for incoming data connections. Whether to bind or connect is determined based on whether the url specifies a wildcard address (bind) or not (connect). | |
| outgoing_url, outoging_url_1 .. outoging_url_256 | Specifies endpoint addresses that should be used for outgoing data connections. Whether to bind or connect is determined based on whether the url specifies a wildcard address (bind) or not (connect). |
The following socket options are hard-coded at present, and can not be changed. They apply to all sockets opened by the transport.
| Socket Option | Value | Description |
|---|---|---|
| ZMQ_RCVHWM | 0 | High-water mark for incoming messages, above which ZeroMQ will take corrective action. A value of zero means no limit, and this is also the ZeroMQ default. |
| ZMQ_SNDHWM | 0 | High-water mark for outgoing messages, above which ZeroMQ will take corrective action. A value of zero means no limit, and this is also the ZeroMQ default. |
| ZMQ_BACKLOG | 200 | Maximum number of pending connections. |
| ZMQ_LINGER | 0 | Specifies that any pending messages should be discarded when the socket is closed. |
| ZMQ_IDENTITY | The sockets' identity property is set to a string that can be useful when debugging (e.g., "dataPub"). |