action.skip

Installing Databridge Client for Kafka

Important

The tar file for the kafka Client is now located in the Linux folder on the release medium.

The Databridge Client for Kafka is installed in the same manner as the Linux Databridge Client for Oracle. Unlike earlier versions (6.6 and 7.0) that used an Oracle database to store metadata, the 7.1 Kafka Client uses an embedded SQLite database to store metadata. It differs in that the replicated data are located in Kafka topics.

A Windows version of the Kafka client is included in the 7.1 Windows installer. Simply select Kafka from the "Feature Selection" tab.

Both the Windows and Linux versions of the Kafka client can be run using the Service/Daemon and the Administrative Console.

Updating Databridge Client for Kafka

On Windows, install the patch for a Hot Fix, Update, or Service Pack, and start the service when done.

On Linux, you need to replace the directory where the tar file was extracted to. We recommend renaming the old install directory, creating a new one, and extracting the tar file into it.

Upgrading from earlier versions

To upgrade from an earlier version (6.6 and 7.0) of the Kafka Client, you need to use the old Client to create an unload file of the Client control tables for all the data sources before you install the 7.1 software. Use the unload command as follows:

dbutility unload _all ControlTables.cct

Once the 7.1 software is installed, follow these steps:

  1. Create a new working directory (for example /opt/dbridge71/work).

  2. Create the directory /etc/MicroFocus/Databridge/7.1

  3. Copy the file globalprofile.ini from the old directory in /etc/Microfocus/Databridge/6.6 or /etc/Microfocus/Databridge/7.0 to the 7.1 directory created in step 2.

    Update the INSTALLDIR and WORKINGDIR entries to point to the directories for the 7.1 software.

  4. Copy the data source directories from the old working directory to the new one created in step 1. You may want to delete the old log files while doing this.

  5. Change the current directory to the directory where the unload file is located.

  6. Run a dbutility configure command to create the control tables in the SQLite database.

  7. Reload the control tables from the unload file using the command dbutility reload _all ControlTables.cct

At this point, you should be ready to resume processing.