If your cluster includes a firewall that prevents or limits Internet access, you can set up local repositories to deploy Ambari and HDP.
Before deploying HDP on a cluster having no or limited Internet access:
Review your deployment strategies.
Compare specific deployment options.
Write down the Base URL of the local mirror repository for each operating system. You select these Base URLs during the cluster install procedure.
For example, if your system includes hosts running CentOS 6, pointed to a HDP 2.0.10.0 repository, your local repository Base URL would look something like this:
http://{your.hosted.local.repository}/HDP-2.0.10.0/repos/centos6
![[Important]](../common/images/admon/important.png)
Important Each relative path must reference your local repository configuration. If your cluster includes multiple operating systems (for example, CentOS 6 and RHEL 6), you must configure a unique repository for each OS. A host in your cluster can retrieve software packages only from a repository configured for that operating system.
Choose a JDK version to deploy, how to download it, and where to install it on each host. See JDK Requirements for more information on supported JDKs.
If you have not already installed the JDK on all hosts, and plan to use Oracle JDK 1.7, download jdk-7u45-linux-x64.tar.gz to
/var/lib/ambari-server/resources.If you plan to use a JDK other than Oracle JDK 1.7, you must install that JDK on each host in your cluster.
Set the Java Home path on each host, using -j option when running
ambari-server setup. See Setup Options for more information about using the -j option to set JAVA_Home.![[Note]](../common/images/admon/note.png)
Note If you have already installed the JDK on all your hosts, you must include the -j option when running
ambari-server setup.
Set up local repositories for Ambari, and HDP based on your preferred strategy, as described in one of the following sections:
