Meta Integration® Model Bridge (MIMB)
"Metadata Integration" Solution

MIMB Bridge Documentation

MIMB Import Bridge from Apache Kafka

Bridge Specifications

Vendor Apache
Tool Name Kafka
Tool Version Kafka 2.x to 3.x
Tool Web Site
Supported Methodology [File System] Multi-Model, Data Store (NoSQL / Hierarchical, Physical Data Model) via Java API on Kafka File

Tool: Apache / Kafka version Kafka 2.x to 3.x via Java API on Kafka File
Metadata: [File System] Multi-Model, Data Store (NoSQL / Hierarchical, Physical Data Model)
Component: ApacheKafka version 11.0.0

This bridge requires internet access to (and exceptionally a few other tool sites)
in order to download the necessary third party software libraries into $HOME/data/download/MIMB/
- If https fails, the bridge then tries with http.
- If a proxy is used to access internet, you must configure that proxy in the JRE (see the -j option in the Miscellaneous parameter).
- If the bridge does not have access to internet, that directory can be copied from another server with internet access.
By running this bridge, you hereby acknowledge responsibility for the license terms and any potential security vulnerabilities from these downloaded third party software libraries.

Loads metadata from all or specified Kafka topics.

When using Confluent Schema Registry specify its URLs in the "Schema Registry URL" parameter.
Otherwise, each topic is assumed to have messages of the same type.
The bridge samples multiple latest messages to determine their common structure.
This bridge supports the following message formats:
- Delimited File (CSV)
- Open Office Excel (XSLX)
- COBOL Copybook
- JSON (JavaScript Object Notation)
- Apache Avro
- Apache Parquet
- Apache ORC

as well as the compressed versions of the above formats:
- ZIP (as a compression format, not as archive format)
- LZ4
- Snappy (as standard Snappy format, not as Hadoop native Snappy format)


Refer to the current general known limitations at or bundled in Documentation/ReadMe/MIMBKnownLimitations.html
When you run both Kafka cluster (server) version 1.1.x and the bridge (client) on Windows systems the import could fail with a timeout error. The Kafka version 2.0.x resolved the issue.

When connecting to Kafka using:
"PLAIN authentication"
Specify 'JAAS configuration path' and leave empty 'Kafka brokers principal name' parameter.

"KERBEROS authentication"
Specify specify values of both parameters.

"without authentication"
Leave both of these parameters empty.

Please refer to the individual parameter's documentation for more details.

Provide a trouble shooting package with:
- the debug log (can be set in the UI or in conf/ with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with option -backup)

Bridge Parameters

Parameter Name Description Type Values Default Scope
Driver version Choose driver version according to Kafka API.
Used to load the necessary version-specific libraries.
Bootstrap servers List of 'host:port' pairs to use for establishing the initial connection to the Kafka cluster, and finding available servers and topics, e.g.
'host1:port1, host2:port2'

The list does not need to include all available servers but should have at least one.
You may want to include more than one server in case any of them are down.
STRING   localhost:9092 Mandatory
Schema Registry URL Comma-separated list of URLs for Schema Registry instances that can be used to look up schemas.
See for details.
STRING   http://localhost:8081  
Topics List of topic names, such as 'topic1, topic2'.
If list is empty, then all topics are available.
You can specify topic names as an wildcard pattern:


Number of sample messages The maximum number of messages to sample from topics. These messages are used to identify topic format details, like field names and data types. STRING   1000  
Use SSL protocol to connect Set this parameter to True when the Kafka consumer uses TLS/SSL to encrypt Kafka's network traffic.

Kafka uses SSL to encrypt connections between the server and clients
Truststore file The location of the trust store file.
If it is empty the bridge would try to locate it in 'java.home'\lib\security\{'jssecacerts'|'cacerts'}
FILE *.*    
Password of the truststore Password of the truststore. PASSWORD      
JAAS configuration path Enter the primary part of the Kerberos principal you defined for the brokers when you were creating the broker cluster. For example, in this principal kafka/, the primary part to be used to fill in this field is kafka.

Kafka property value -
FILE *.*    
Kafka brokers principal name Enter the primary part of the Kerberos principal you defined for the brokers when you were creating the broker cluster. For example, in this principal kafka/, the primary part to be used to fill in this field is kafka.
This value is going to Kafka property:
kinit command path Kerberos uses a default path to its kinit executable. If you have changed this path, select this check box and enter the custom access path.

Kafka property value -
Kerberos configuration path Kerberos uses a default path to its configuration file, the krb5.conf file (or krb5.ini in Windows) for Kerberos 5 for example. If you leave this parameter clear, a given strategy is applied by Kerberos to attempt to find the configuration information it requires.
For details about this strategy, see the Locating the krb5.conf Configuration File section in Kerberos requirements.

This value is going to JVM -
FILE *.*    
Miscellaneous Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g.
-connection.cast MyDatabase1="SQL Server"
Some options can be used multiple times if applicable, e.g.
-connection.rename NewConnection1=OldConnection1 -connection.rename NewConnection2=OldConnection2;
As the list of options can become a long string, it is possible to load it from a file which must be located in ${MODEL_BRIDGE_HOME}\data\MIMB\parameters and have the extension .txt. In such case, all options must be defined within that file as the only value of this parameter, e.g.


Bridge Mapping

Mapping information is not available

Last updated on Fri, 25 Sep 2020 17:37:51

Copyright © Meta Integration Technology, Inc. 1997-2020 All Rights Reserved.

Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.