Using a Local, Shared Repository With the Installer
The Installer can use a local repository instead of an internet repository.
When you run the mapr-setup.sh script, it attempts to connect to
                    https://package.ezmeral.hpe.com/ and configures an internet repository. If there is no internet
            connectivity, the script asks for archive files so that it can create a local
            repository.
-a <full path each archive file> to the
                    mapr-setup.sh script bypasses the internet connectivity check
                and automatically creates a local repository with the provided archive files.To install with a local, shared repository, the node that runs
                mapr-setup.sh needs the following:
- Any OS dependencies or Java Development Kit (JDK) packages that are required.
 - A webserver. The script attempts to install a webserver on the node if a
                webserver is not available. The webserver is needed to provide the package files to
                each node in the cluster. Note that this webserver is not configured to start
                automatically after a server restart. However, you can start the webserver manually
                by using the 
systemctl start httpdcommand. - Archive file(s). To install release 5.2 and later, you need to download
                mutiple archive files. 
For release 5.2 and later - The Core archive file. Download the archive file
                                                
mapr-<version>GA.<dep|rpm>.tgzfrom one of the following locations, based on the operating system of the node:https://package.ezmeral.hpe.com/releases/v.<version>/redhat/https://package.ezmeral.hpe.com/releases/v.<version>/ubuntu/https://package.ezmeral.hpe.com/releases/v.<version>/suse/
NOTEThe packagemapr-v<version>GA-upgrade.<rpm/deb>.tgzis not for use with the Installer. - The Installer archive file. Based on the
                                            operating system of the node, download
                                                
mapr-installer-<version>.<yyyymmdd>.<dep|rpm>.tgzfrom one of the following locations: - The Ecosystem Pack (EEP) archive
                                                file. Based on the operating system of the node,
                                            download
                                                
mapr-mep-<version>.<yyyymmdd>.<dep|rpm>.tgzfrom one of the following locations: 
The MEP-<version> directory can be represented by a 2-digit number or a 3-digit number. The 3-digit directory contains a fixed MEP version, including patches, and is not continuously updated. The 2-digit EEP directory points to the latest MEP and patches and is continuously updated. See Understanding Two-Digit and Three-Digit EEPs.
 - The Core archive file. Download the archive file
                                                
 - The 
mapr-setup.shscript. 
- clustershell
 - pdsh
 - pdsh-rcmd-ssh
 - sshpass*
 
*Before installing a cluster on a SLES image, you must install sshpass,
            as described in Adding the Data Fabric Repository on SUSE.
mapr-setup.sh script and the archive files to the
            node that will run the Installer, run the following command from the directory that
            contains the mapr-setup.sh
            script:bash ./mapr-setup.sh -a <full path to the archive files>