Setting up CMA server

You must create a docker image to run the Clouder Migration Assistant server or install it locally. You can deploy it to any of your cluster nodes or an external node that has visibility to the cluster and has at least 1.5 GB of extra memory. ${cloudera.version} here represents the CMA versions such as and so on.

To identify the exact filename of the archive, open${cloudera.version}/tars/ and see the archive file available.

Downloading CMA

Download the latest CMA binaries from The supported version of CMA is and higher.

wget${base.version}/tars/cma-${cloudera.version}-bin.tar.gz or curl${base.version}/tars/cma-${cloudera.version}-bin.tar.gz --output cma-${cloudera.version}-bin.tar.gz

Extract and unzip the CMA archive: tar xzf cma-${cloudera.version}-bin.tar.gz

Starting CMA server

After extracting the compressed file, there are two ways to start the CMA server - in a docker container or locally.

Starting CMA server in Docker Container

Run the script in the untarred top-level folder to launch the CMA server in a docker container. cma-${cloudera.version}/bin/ --start

Starting CMA server locally

Ensure that Python 3.8 or later and Java runtime version 11 are installed on the host.

Run the script in the untarred top-level folder and follow its instructions to launch the CMA server locally. cma-${cloudera.version}/bin/ --start

After startup

After the CMA server starts, open
in a browser. Cloudera Migration Assistant (CMA) Server opens.
This confirms that Cloudera Migration Assistant (CMA) Server is successfully installed.