.. _migrate-ak-cc: Migrate from |ak| or |cp| Community Edition ########################################### If you are already running |ak-tm| or the community features that Confluent offers, and want to use some of Confluent's enterprise services, you can easily migrate from |ak| or |cp| Community Edition to |cs|. The next sections show you the steps to migrate to |cs|. Note that |cs| requires that the ``confluent.license`` property be set to a valid license string in each broker properties file, and this license is checked at broker start up. For more information, see :ref:`cp-license-overview`. .. _migrate-kafka: Migrate an Existing |ak| Deployment to |cp| =========================================== This section describes migrating from open-source |ak| to |cp|. You should start the migration by assessing your current |ak| deployment; the version of |ak|, and |ak| components and configuration files you are currently using. The version of |ak| in |cp| is fully compatible with the matching open source version and only contains additional patches for critical bugs when |cp| and |ak| release schedules do not align. For version compatibility, see :ref:`cp-ak-compatibility`. You should migrate to a compatible version, and if you want to upgrade, do so after you migrate. An existing cluster can typically be upgraded easily by performing a :ref:`rolling restart ` of |ak| brokers. Download the |cp| packages ^^^^^^^^^^^^^^^^^^^^^^^^^^ Download and install the |cp| archive that contains the entire platform. The next steps describe downloading a TAR or ZIP archive. For all of the installation options, see :ref:`installation`. #. Download the correct version of the |cp| TAR or ZIP archive from :cp-download:`https://www.confluent.io/download/|`. #. Extract the contents of the archive into a new |cp| install directory. For ZIP files, use a GUI to extract the contents or run this command in a terminal: .. codewithvars:: bash unzip confluent-|release|.zip For TAR files run this command: .. codewithvars:: bash tar xzf confluent-|release|.tar.gz #. Copy all configuration files from the |ak| ``./config`` directory into the ``./etc/kafka`` folder under the new |cp| directory you created in the previous step. #. Stop all |ak| services running in the |ak| directory. This might include ``kafka-server`` and ``zookeeper-server``. #. Start the corresponding services in the |cp| directory, and in addition start any Confluent enterprise services you want to use, for example ``confluent-control-center``. Similar to |ak|, the start and stop scripts for all services are found in the ``./bin`` directory. #. Repeat these steps on each server, one server at a time, to perform rolling migration. #. If at any time you want to move back to |ak|, simply stop the services in the |cp| installation directory and start them in the |ak-tm| directory. Add additional tools and features ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Remaining |cp| services can be added incrementally. For example, start by adding |sr| and updating your applications to use the Avro serializer. You can also add the REST Proxy to support applications that may not have access to good |ak| clients or Avro libraries. Run the HDFS connector to load data from |ak| into HDFS continuously. For an overview of all the features that |cp| provides, see :ref:`cp-features`. .. _enterprise_migration: Migrate from |cc| to full |cp| ============================== This section covers migrating from |cc| to full |cp|. Download new packages ^^^^^^^^^^^^^^^^^^^^^ The first step of migration is to install additional components, or download new |cp| packages. DEB Packages via apt or RPM Packages via yum ********************************************* If you installed |cc-components| with yum or apt-get, you can use a yum command to install additional enterprise components. This is because the |cp| packages that contain everything in |cc-components| plus additional enterprise packages. Install the additional enterprise packages in your existing community deployment by running: .. codewithvars:: bash sudo yum install confluent-platform or .. codewithvars:: bash sudo apt-get install confluent-platform TAR or ZIP archives ******************* If you installed |cc-components| from TAR or ZIP archives, you must download and install a new |cp| archive that contains the entire platform. #. Download the |cp| TAR or ZIP archive from :cp-download:`https://www.confluent.io/download/|`. #. Extract the contents of the archive into a new |cp| install directory. For ZIP files, use a GUI to extract the contents or run this command in a terminal: .. codewithvars:: bash unzip confluent-|release|.zip .. codewithvars:: bash tar xzf confluent-|release|.tar.gz Finish the migration ^^^^^^^^^^^^^^^^^^^^^ Use the following steps to finish the migration process. #. Copy all configuration files from ``./etc``, including ``./etc/kafka``, ``./etc/kafka-rest``, ``./etc/schema-registry``, and ``./etc/confluent-control-center`` into the new directory you created in previous step. #. Stop all |ak-tm| services running in the |cc-components| directory. Depending on what was running, this will include ``kafka-rest``, ``schema-registry``, ``connect-distributed``, ``kafka-server`` and ``zookeeper-server``. #. Start the corresponding services in the new |cp| directory, and in addition start any new Enterprise services you want to use - for example ``confluent-control-center``. #. Repeat these steps on all Confluent servers, one server at a time, to perform rolling migration. #. If at any time you want to move back to |cc-components|, simply stop the services in the |cp| installation directory and start them in the |cc-components| directory. Related content *************** - :ref:`migrate-confluent-server` - :ref:`cp-license-overview` - :ref:`migrate-zk-kraft`