Skip to content


This section contains parameters specific to Databridge Client for Kafka.


Default: ""

DMSII data set to Kafka topic mapping is controlled by the configuration file topic_config.ini. This file is created during the generate phase of the replication process. If most or all of the data sets are going to be written to a single topic, then the dbridge.ini file parameter default_topic can be used to set the topic for all of the data sets. If default_topic is omitted, then each data set will be assigned a topic that is comprised of the data source and data set name separated by an underscore.


Default: ""

The kafka_broker parameter consists of a comma separated list of brokers. This can be a partial list as the client will query cluster metadata information to obtain the full list of brokers and leaders.


Default: ""

The kafka_debug parameter controls the debugging contexts within the Kafka module. It consists of a comma separated list of one or more of the following: generic, broker, topic, metadata, feature, queue, msg, protocol, cgrp, security, fetch, interceptor, plugin, consumer, admin, eos, and all. This parameter is normally commented out and should be activated under the guidance of Micro Focus Customer Care support.


Default: True

The ltrim_zeroes parameter controls whether or not to strip leading zeroes from numbers in the output stream.


Default: scientific, 11, 6

The real_format parameter has 3 arguments, which specify the format type, the length, and the scale to use when formatting a DMSII REAL. The format type can be either scientific or decimal, just like in DBSupport. The remaining two arguments are the length and scale, which allow you to further control the format used to write to the output stream.


Default: True

The rtrim_spaces parameter controls whether or not to strip trailing blanks in strings written to the output stream. This parameter can be augmented by the [Params] section parameter set_blanks_to_null, which causes blank items to be represented as null.


Default: "PLAINTEXT"

The security_protocol parameter determines how the Databridge Kafka Client will communicate with the Kafka broker. This required parameter may be one of the following:

  • PLAINTEXT -- no authentication or datastream encryption will be used.

  • SASL_PLAINTEXT -- the client will be authenticated with Kerberos, but the datastream will not be encrypted.

  • SSL -- the datastream will be encrypted but the client will not be authenticated.

  • SASL_SSL -- the client will be authenticated and the datastream will be encrypted.


Default: ""

This parameter specifies the location of the CA certificate file to verify the broker's certificate.


Default: ""

This parameter specifies the location of the client's certificate PEM file.


Default: ""

This parameter specifies the location of the client's key file.


Default: ""

This parameter allows one to specify the key file password if needed. After a dbutility export, this parameter will be encoded.


Default: "'"

This parameter sets the Kafka Kerberos service name. The default value is "kafka".


Default: ""

This parameter sets the client's keytab location. You must create the client principal and keytab file, then securely copy the keytab file to the client host. For example, using kadmin.local and the names in the sample dbridge.ini file below:

# kadmin.local -q 'addprinc -randkey dbclient/'
# kadmin.local -q 'ktadd -k /etc/security/keytabs/dbclient.keytab dbclient/


Default: "'"

This parameter sets the client principal name. For example, from the sample dbridge.ini above: dbclient/


Default: ""

The span_date_delim parameter allows the year, month, and day to be separated either by slashes, dashes, or dots (or not separated at all). If you use a date delimiter, then the hours, minutes and seconds will be separated by colons and the time part will be preceded by a blank. If the delimiter is the empty string, then they are all run together to form a 14-digit number.


Default: 21

The span_date_format parameter, in conjunction with the span_date_delim and span_date_scale parameters, defines how dates are represented in the output stream. The format uses the same date format codes as the standard Client. Currently, only the format with 4-digit years is supported.


Default: 0

The span_date_scale parameter specifies how many digits after the seconds are to be added to represent fractions of seconds. When the scale is greater than zero a decimal character (dot or comma) is added after the seconds.


Default: real

The treat_real_as parameter indicates how the define and redefine commands are to treat all REAL items that are not customized. This parameter allows you to do this without the need to do any customization using SQL user scripts. There are 3 choices available: (1) a value of real indicates that a REAL should be treated as a floating point number; (2) a value time6 indicates that a REAL should be treated as a TIME(6) value; (3) a value of binary indicates that a REAL should be written out to the output stream as 12-hex digits, just like an RSN. If you have REAL items in DMSII that are timestamps, you need to treat them as BINARY (if you know that they are TIME(6) data, you can treat them as such). If you just treat them as REAL, the most significant bit of the item will be lost when the number is converted to scientific or decimal format, as this bit is unused for a floating point values on the A-Series machines. On the other hand timestamps use this bit, which is typically part of the date.


Default: False

The use_plus_sign parameter is a boolean that controls whether or not positive signed numbers are always preceded by a + sign.