In Installation Path A, Cloudera Manager automates the installation of the Oracle JDK, Cloudera Manager Server, embedded PostgreSQL database, Cloudera Manager Agent,
CDH, and managed service software on cluster hosts. Cloudera Manager also configures databases for the Cloudera Manager Server and Hive Metastore and optionally for Cloudera Management Service roles.
This path is recommended for demonstration and proof-of-concept deployments, but is not recommended for production deployments because its not intended to scale and may require
database migration as your cluster grows. To use this method, server and cluster hosts must satisfy the following requirements:

The automated installer binary (cloudera-manager-installer.bin) installs the highest version of Cloudera Manager. To use a lower version, you must
install Cloudera Manager using packages. See Installing Lower Versions of Cloudera Manager 5.

Provide the ability to log in to the Cloudera Manager Server host using a root account or an account that has password-less sudo permission.

Configure an HTTP Proxy

The Cloudera Manager installer accesses archive.cloudera.com by using yum on RHEL
systems, zypper on SLES systems, or apt-get on Debian/Ubuntu systems. If your hosts access the Internet through an HTTP proxy, you can
configure yum, zypper, or apt-get, system-wide, to access archive.cloudera.com through a proxy. To do so, modify the system configuration on the Cloudera Manager Server host and on every cluster host as follows:

OS

File

Property

RHEL-compatible

/etc/yum.conf

proxy=http://server:port/

SLES

/root/.curlrc

--proxy=http://server:port/

Ubuntu or Debian

/etc/apt/apt.conf

Acquire::http::Proxy "http://server:port";

Install the Oracle JDK

If you choose not to have the Oracle JDK installed by Cloudera Manager, install the JDK on all hosts in the cluster according to the following instructions:

Start and Log into the Cloudera Manager Admin Console

The Cloudera Manager Server URL takes the following form http://Server
host:port, where Server host is the fully qualified domain name (FQDN) or IP address of the host where the Cloudera
Manager Server is installed, and port is the port configured for the Cloudera Manager Server. The default port is 7180.

Wait several minutes for the Cloudera Manager Server to start. To observe the startup process, run tail -f
/var/log/cloudera-scm-server/cloudera-scm-server.log on the Cloudera Manager Server host. If the Cloudera Manager Server does not start, see
Troubleshooting Installation and Upgrade Problems.

In a web browser, enter http://Server host:7180, where Server host is the FQDN or IP address of the host where the Cloudera Manager Server is running.

The login screen for Cloudera Manager Admin Console displays.

Log into Cloudera Manager Admin Console. The default credentials are: Username:adminPassword:admin. Cloudera Manager does not support changing the admin username for the installed account. You can change
the password using Cloudera Manager after you run the installation wizard. Although you cannot change the admin username, you can add a new user, assign administrative
privileges to the new user, and then delete the default admin account.

After you log in, the Cloudera Manager End User License Terms and Conditions page displays. Read the terms and
conditions and then select Yes to accept them.

Click Continue.

The Welcome to Cloudera Manager page displays.

Use the Cloudera Manager Wizard for Software Installation and Configuration

The following instructions describe how to use the Cloudera Manager installation wizard to do an initial installation and configuration. The wizard lets you:

Select the edition of Cloudera Manager to install

Find the cluster hosts you specify using hostname and IP address ranges

Connect to each host with SSH to install the Cloudera Manager Agent and other components

Optionally install the Oracle JDK on the cluster hosts.

Install CDH and managed service packages or parcels

Configure CDH and managed services automatically and start the services

Important: All hosts in the cluster must have some way to access installation files using one of the following methods:

Internet access to allow the wizard to install software packages or parcels from archive.cloudera.com.

Choose Cloudera Manager Edition

Cloudera Express, which does not require a license, but provides a limited set of features.

Cloudera EnterpriseEnterprise Data Hub Edition Trial, which does not require a license, but expires after 60 days and cannot be
renewed.

Cloudera Enterprise with one of the following license types:

Basic Edition

Flex Edition

Enterprise Data Hub Edition

If you choose Cloudera Express or Cloudera EnterpriseEnterprise Data Hub Edition Trial, you can upgrade the license at a later
time. See Managing Licenses.

If you elect Cloudera Enterprise, install a license:

Click Upload License.

Click the document icon to the left of the Select a License File text field.

Go to the location of your license file, click the file, and click Open.

Click Upload.

Information is displayed indicating what the CDH installation includes. At this point, you can click the Support
drop-down menu to access online Help or the Support Portal.

Click Continue to proceed with the installation.

Choose Cloudera Manager Hosts

Choose which hosts will run CDH and managed services:

To enable Cloudera Manager to automatically discover hosts on which to install CDH and managed services, enter the cluster hostnames or IP addresses.
You can also specify hostname and IP address ranges. For example:

You can specify multiple addresses and address ranges by separating them with commas, semicolons, tabs, or blank spaces, or by placing them on separate lines. Use this technique to make
more specific searches instead of searching overly wide ranges. The scan results will include all addresses scanned, but only scans that reach hosts running SSH will be selected for inclusion in your
cluster by default. If you do not know the IP addresses of all of the hosts, you can enter an address range that spans over unused addresses and then clear the hosts that do not exist (and are not
discovered) later in this procedure. However, keep in mind that wider ranges will require more time to scan.

Click Search. Cloudera Manager identifies the hosts on your cluster to allow you to configure them for services. If
there are a large number of hosts on your cluster, wait a few moments to allow them to be discovered and shown in the wizard. If the search is taking too long, you can stop the scan by clicking
Abort Scan. To find additional hosts, click New Search, add the host names or IP addresses and click Search
again. Cloudera Manager scans hosts by checking for network connectivity. If there are some hosts where you want to install services that are not shown in the list, make sure you have network
connectivity between the Cloudera Manager Server host and those hosts. Common causes of loss of connectivity are firewalls and interference from SELinux.

Verify that the number of hosts shown matches the number of hosts where you want to install services. Clear host entries that do not exist and clear
the hosts where you do not want to install services.

Choose Software Installation Method and Install Software

Important: You cannot install software using both parcels and packages in the same cluster.

Select the repository type to use for the installation. In the Choose Method section select one of the following:

Use Parcels

Choose the parcels to install. The choices you see depend on the repositories you have chosen – a repository may contain multiple parcels. Only the
parcels for the latest supported service versions are configured by default.

You can add additional parcels for previous versions by specifying custom repositories. For example, you can find the locations of the previous CDH 4 parcels at https://archive.cloudera.com/cdh4/parcels/. Or, if you are installing CDH 4.3 and want to use policy-file authorization, you can add the Sentry parcel using this mechanism.

To specify the Parcel Directory or Local Parcel Repository Path, add a parcel repository, or specify the properties
of a proxy server through which parcels are downloaded, click the More Options button and do one or more of the following:

Parcel Directory and Local Parcel Repository Path - Specify the location of parcels on cluster hosts and the Cloudera
Manager Server host.

Parcel Repository - In the Remote Parcel Repository URLs field, click the button and enter the URL of the repository. The URL you specify is added to the list of repositories listed in the Configuring Cloudera Manager Server Parcel Settings page and a parcel is added to the list of parcels on the Select Repository page. If
you have multiple repositories configured, you will see all the unique parcels contained in all your repositories.

Proxy Server - Specify the properties of a proxy server.

Click OK. Parcels available from the configured remote parcel repository URLs are displayed in the parcels list. If you specify a URL for a parcel version
too new to be supported by the Cloudera Manager version, the parcel is not displayed in the parcel list.

Use Packages

Select the major release of CDH to install.

Select the specific release of CDH to install. You can choose either the latest version, a specific version, or use a custom repository. If you specify a custom repository for a CDH
version too new to be supported by the Cloudera Manager version, Cloudera Manager will install the packages but you will not be able to create services using those packages and will have to manually
uninstall those packages and manually reinstall packages for a supported CDH version.

Select the specific releases of other services to install. You can choose either the latest version or use a custom repository. Choose None if you do not
want to install that service.

If you are using Cloudera Manager to install software, select the release of Cloudera Manager Agent. You can choose either the version that matches the
Cloudera Manager Server you are currently using or specify a version in a custom repository. If you opted to use custom repositories for installation files, you can provide a GPG key URL that applies
for all repositories.

Click Continue.

The Cluster Installation JDK Installation Options screen displays.

Select Install Oracle Java SE Development Kit (JDK) to allow Cloudera Manager to install the JDK on each cluster host. If
you have already installed the JDK, do not select this option. If your local laws permit you to deploy unlimited strength encryption, and you are running a secure cluster, select the Install Java Unlimited Strength Encryption Policy Files checkbox.
Note: If you already manually installed the JDK on each cluster host, this option to install the JDK does not display.

Click Continue.

(Optional) Select Single User Mode to configure the Cloudera Manager Agent and all service processes to run as the
same user. This mode requires extra configuration steps that must be done manually on all hosts in the cluster. If you have
not performed the steps, directory creation will fail in the installation wizard. In most cases, you can create the directories but the steps performed by the installation wizard may have to be
continued manually. Click Continue.

Specify host installation properties:

Select root or enter the username for an account that has password-less sudo permission.

Select an authentication method:

If you choose password authentication, enter and confirm the password.

If you choose public-key authentication, provide a passphrase and path to the required key files.

You can specify an alternate SSH port. The default value is 22.

You can specify the maximum number of host installations to run at once. The default value is 10.

Click Continue. Cloudera Manager performs the following:

Parcels - installs the Oracle JDK and the Cloudera Manager Agent packages and starts the Agent. Click Continue.
During parcel installation, progress is indicated for the phases of the parcel installation process in separate progress bars. If you are installing
multiple parcels, you see progress bars for each parcel. When the Continue button at the bottom of the screen turns blue, the installation process is
completed.

Packages - configures package repositories, installs the Oracle JDK, CDH and managed service and the Cloudera Manager Agent packages, and starts the
Agent. When the Continue button at the bottom of the screen turns blue, the installation process is completed. If the installation has completed successfully on some
hosts but failed on others, you can click Continue if you want to skip installation on the failed hosts and continue to the next screen to start configuring services
on the successful hosts.

While packages are being installed, the status of installation on each host is displayed. You can click the Details link for individual hosts to view detailed
information about the installation and error messages if installation fails on any hosts. If you click the Abort Installation button while installation is in progress,
it will halt any pending or in-progress installations and roll back any in-progress installations to a clean state. The Abort Installation button does not affect host
installations that have already completed successfully or already failed.

Click Continue.

The Host Inspector runs to validate the installation and provides a summary of what it finds, including all the versions of the installed components. If
the validation is successful, click Finish.

Add Services

In the first page of the Add Services wizard, choose the combination of services to install and whether to install Cloudera Navigator:

Some services depend on other services; for example, HBase requires HDFS and ZooKeeper. Cloudera Manager tracks dependencies and installs the correct combination of services.

In a Cloudera Manager deployment of a CDH 4 cluster, the MapReduce service is the default MapReduce computation framework. Choose Custom
Services to install YARN, or use the Add Service functionality to add YARN after installation completes.
Note:You can create a YARN service in a CDH 4 cluster, but it is not considered production ready.

In a Cloudera Manager deployment of a CDH 5 cluster, the YARN service is the default MapReduce computation framework. Choose Custom
Services to install MapReduce, or use the Add Service functionality to add MapReduce after installation completes.
Note:In CDH 5, the MapReduce service has been deprecated. However, the MapReduce service is fully supported for backward
compatibility through the CDH 5 lifecycle.

The Flume service can be added only after your cluster has been set up.

Customize the assignment of role instances to hosts. The wizard evaluates the hardware configurations of the hosts to determine the best hosts for each
role. The wizard assigns all worker roles to the same set of hosts to which the HDFS DataNode role is assigned. You can reassign role instances if necessary.

Click a field below a role to display a dialog box containing a list of hosts. If you click a field containing multiple hosts, you can also select All Hosts
to assign the role to all hosts, or Custom to display the pageable hosts dialog box.

The following shortcuts for specifying hostname patterns are supported:

Click the View By Host button for an overview of the role assignment by hostname ranges.

When you are satisfied with the assignments, click Continue.

Configure Database Settings

Choose the database type:

Keep the default setting of Use Embedded Database to have Cloudera Manager create and configure required databases. Record the auto-generated
passwords.

Select Use Custom Databases to specify external database host, enter the database type, database name, username, and password for the database that you
created when you set up the database.

If you are adding the Oozie service, you can change your Oozie configuration to control when data is purged to improve performance, cut down on database disk usage, improve upgrade
performance, or to keep the history for a longer period of time. See Configuring Oozie Data Purge Settings Using Cloudera
Manager.

Click Test Connection to confirm that Cloudera Manager can communicate with the database using the information you have
supplied. If the test succeeds in all cases, click Continue; otherwise, check and correct the information you have provided for the database and then try the test
again. (For some servers, if you are using the embedded database, you will see a message saying the database will be created at a later step in the installation process.)

The Cluster Setup Review Changes screen displays.

Review Configuration Changes and Start Services

Review the configuration changes to be applied. Confirm the settings entered for file system paths. The
file paths required vary based on the services to be installed. If you chose to add the Sqoop service, indicate whether to use the default Derby database or the embedded PostgreSQL database.
If the latter, type the database name, host, and user credentials that you specified when you created the database.
Warning: Do not place DataNode data directories on NAS devices. When resizing an NAS, block replicas can be deleted, which will result in
reports of missing blocks.

Click Continue.

The wizard starts the services.

When all of the services are started, click Continue. You see a success message indicating that your cluster has been
successfully started.

Change the Default Administrator Password

Click the logged-in username at the far right of the top navigation bar and select Change Password.

Enter the current password and a new password twice, and then click OK.

Configure Oozie Data Purge Settings

If you added an Oozie service, you can change your Oozie configuration to control when data is purged to improve performance, cut down on database disk usage, or to keep the history for
a longer period of time. Limiting the size of the Oozie database can also improve performance during upgrades. See Configuring Oozie
Data Purge Settings Using Cloudera Manager.

If this documentation includes code, including but not limited to, code examples, Cloudera makes this available to you under the terms of the Apache License, Version 2.0, including any required
notices. A copy of the Apache License Version 2.0 can be found here.