forked from docs/doc-exports
Chen, Junjie
5bb11b7c7f
Reviewed-by: Antonova, Ekaterina <ekantono@noreply.gitea.eco.tsi-dev.otc-service.com> Co-authored-by: Chen, Junjie <chenjunjie@huawei.com> Co-committed-by: Chen, Junjie <chenjunjie@huawei.com>
26 lines
5.0 KiB
HTML
26 lines
5.0 KiB
HTML
<a name="Kafka-config"></a><a name="Kafka-config"></a>
|
|
|
|
<h1 class="topictitle1">Collecting Connection Information</h1>
|
|
<div id="body1552118864471"><p id="Kafka-config__p1330823020346">Before accessing a Kafka instance for message production and consumption, obtain the following information of the instance.</p>
|
|
<div class="section" id="Kafka-config__section539013221352"><h4 class="sectiontitle">Instance Connection Address and Port</h4><p id="Kafka-config__p14733142285020">Obtain them from the <strong id="Kafka-config__b2078511598232">Basic Information</strong> page on the Kafka console.</p>
|
|
<p id="Kafka-config__p204638583020">For a cluster Kafka instance that has at least three connection addresses, you are advised to configure all of the connection addresses on the client for high reliability.</p>
|
|
<p id="Kafka-config__p72113348403">For public network access, you can use the public network addresses displayed on the <strong id="Kafka-config__b732165725115">Basic Information</strong> page.</p>
|
|
<div class="fignone" id="Kafka-config__fig426811519812"><span class="figcap"><b>Figure 1 </b>Viewing the connection addresses and ports of brokers of a Kafka instance</span><br><span><img id="Kafka-config__image1595564310019" src="en-us_image_0000001949896476.png"></span></div>
|
|
</div>
|
|
<div class="section" id="Kafka-config__section10322144512489"><h4 class="sectiontitle">Topic name</h4><p id="Kafka-config__p187435453419">Obtain the topic name from the <strong id="Kafka-config__b1601948192412">Topics</strong> page of the Kafka instance console.</p>
|
|
<div class="note" id="Kafka-config__note898162205419"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="Kafka-config__p109832235417">If <strong id="Kafka-config__b88602425515">Automatic Topic Creation</strong> is disabled, a topic must be created first. Then a Kafka instance can be accessed from a client for message production and consumption.</p>
|
|
</div></div>
|
|
</div>
|
|
<div class="section" id="Kafka-config__section7834639164915"><h4 class="sectiontitle">Ciphertext Access</h4><p id="Kafka-config__p5360123575015">If ciphertext access is enabled for the instance, obtain the instance username and password, SASL mechanism, and security protocol. In addition, obtain the SSL certificate if the security protocol is set to <strong id="Kafka-config__b1886516841510">SASL_SSL</strong>.</p>
|
|
<ul id="Kafka-config__ul19762115465215"><li id="Kafka-config__li576217546523">Obtain the username on the <strong id="Kafka-config__b1696374711162">Users</strong> page on the Kafka console. If you forget your password, obtain it again by <a href="https://docs.otc.t-systems.com/en-us/usermanual/dms/kafka-ug-0003.html" target="_blank" rel="noopener noreferrer">resetting the password</a>.<div class="fignone" id="Kafka-config__fig107621654205212"><span class="figcap"><b>Figure 2 </b>Obtaining the SASL_SSL username</span><br><span><img id="Kafka-config__image87621954105211" src="en-us_image_0000001980576777.png"></span></div>
|
|
</li><li id="Kafka-config__li6762195415219">Obtain the SASL mechanism from the <strong id="Kafka-config__b961812242457">Basic Information</strong> page on the Kafka console.<div class="p" id="Kafka-config__p2762654195213">If both SCRAM-SHA-512 and PLAIN are enabled, use either of them in connection configurations. For instances that were created much earlier, if <strong id="Kafka-config__b3713111918">SASL Mechanism</strong> is not displayed on the instance details page, PLAIN is used by default.<div class="fignone" id="Kafka-config__fig1376315417529"><span class="figcap"><b>Figure 3 </b>SASL mechanism in use</span><br><span><img id="Kafka-config__image37631954125215" src="en-us_image_0000001980456929.png"></span></div>
|
|
</div>
|
|
</li><li id="Kafka-config__li276319540522">Obtain the security protocol from the <strong id="Kafka-config__b861993811456">Basic Information</strong> page on the Kafka console. For Kafka instances that were created much earlier, if <strong id="Kafka-config__b10493184582217">Security Protocol</strong> is not displayed on the instance details page, SASL_SSL is used by default.<div class="fignone" id="Kafka-config__fig1763105412524"><span class="figcap"><b>Figure 4 </b>Security protocol</span><br><span><img id="Kafka-config__image5763195425218" src="en-us_image_0000001980576785.png"></span></div>
|
|
</li><li id="Kafka-config__li14762125465211">If <strong id="Kafka-config__b46467312350">Security Protocol</strong> is set to <strong id="Kafka-config__b1375502414338">SASL_SSL</strong>, download the certificate from the <strong id="Kafka-config__b151421999352">Basic Information</strong> page on the Kafka console.<p id="Kafka-config__p1076211549522">JKS certificates are used for accessing instances in Java. CRT certificates are used for accessing instances in Python.</p>
|
|
<div class="fignone" id="Kafka-config__fig8662201513266"><span class="figcap"><b>Figure 5 </b>Downloading the SSL certificate</span><br><span><img id="Kafka-config__image9662151572612" src="en-us_image_0000001950565600.png"></span></div>
|
|
</li></ul>
|
|
</div>
|
|
</div>
|
|
<div></div>
|
|
|