Setting up CMA server

You can deploy the Cloudera Migration Assistant (CMA) Server (cma-server) to any of your source CDH cluster nodes, or preferably to an external node that has visibility both to the cluster and the Internet. It requires 1.5 GB of extra memory.

Downloading CMA tool

Download the latest CMA binaries from https://archive.cloudera.com/am2cm/2.8.0/tars. The supported version of the CMA is 2.8.0 and higher.

wget https://archive.cloudera.com/am2cm/2.8/tars/cma-2.8.1.0-12-bin.tar.gz or curl https://archive.cloudera.com/am2cm/2.8/tars/cma-2.8.1.0-12-bin.tar.gz--output cma-2.8.1.0-12.tar.gz

Extract the downloaded file: tar xzf cma-2.8.1.0-12.tar.gz

Starting CMA server

After extracting the compressed file, there are two ways to start the CMA server: in Docker container or locally. The preferred method is the Docker mode.
Starting CMA server in Docker container
Run the cma-docker.sh script in the untarred top-level folder to launch the CMA server in a Docker container. cma-${cloudera.version}/bin/cma-docker.sh --start
Starting CMA server locally
Ensure that Python 3.9.8 or later is installed on the host.
Run the cma-local.sh script in the untarred top-level folder and follow its instructions to launch the CMA server locally. cma-2.8.1.0-12/bin/cma-local.sh --start

After the CMA server starts, open http://localhost:8090 in a browser and the CMA Server opens.

This confirms that the CMA Server is successfully installed.