Stelo Technical Documents

Setting up the Confluent environment

Last Update: 10 Aug 2023
Product: StarQuest Data Replicator
Version: SQDR 6.20 or later
Article ID: SQV00DR053

Objective

The objective of this documents is to setup the Confluent environment as a broker for SQDR to deliver data. This technical document describes the steps needed to setup and gather the required connectivity information for SQDR to connect to the Confluent Cloud environment. For more information on how to setup a Confluent Platform environment, please refer to Confluent Platform for more details.

Table of contents

Prerequisite

Download the following properties file based on the intended environment to be setup down below:

Create the cloud environment

1. Login to Confluent Cloud.

2. Select Add cloud environment and enter the name of the cloud environment to be created.

Create the Confluent cluster

1. Select Create cluster on my own.

2. Select the desired cluster type.

3. Select the cloud provider, region, and type of availability needed.

4. Review the selections made and confirm.

5. Once the cluster has been created, select the created cluster, then select API Keys.

6. Create an API Key that has Global Access to ensure that SQDR has the ability to create topics and write data to the topics.

Create the schema registry

1. Select the environment that was created.

2. Select enable now to create the schema registry.

3. Select the desired schema registry package.

4. After the schema registry has been created, note down the ID in the Confluent Cloud properties file.


5. Select the Add key and create the API key for the schema registry. Once the API key has been created, note them down in the Confluent Cloud properties file.

6. Once the required information is noted, replication can now be setup from SQDR to Confluent Cloud. For more information on how to setup replication to Confluent Cloud, please refer to Streaming to Confluent for more details.


DISCLAIMER

The information in technical documents comes without any warranty or applicability for a specific purpose. The author(s) or distributor(s) will not accept responsibility for any damage incurred directly or indirectly through use of the information contained in these documents. The instructions may need to be modified to be appropriate for the hardware and software that has been installed and configured within a particular organization.  The information in technical documents should be considered only as an example and may include information from various sources, including IBM, Microsoft, and other organizations.