Installing Big Match on Ambari (V11.5.0.4)

After downloading the Big Match installer artifacts, run the setup on the node on a machine that has internet access.

1. Update the permissions on the downloaded *.bin file to enable execute.

   chmod +x <package_name>.bin

2. Run the *.bin file to extract and install the services in the module.

   ./bigmatch_<project_version>.bin

   Note: Run the *.bin file on a Linux system because this file depends on some system packages.
3. After the prompt, agree to the license terms. Reply yes | y to continue with the install.
4. After the prompt, choose if you want to install Big Match online (Option 1), or offline (Option 2).

   Option 1: Hadoop cluster has access to the internet (online mode)

   The program will lay out the Ambari service configuration files and update the repository locations in the Ambari server file, repoinfo.xml.

   Skip to step 6.

   Option 2: Hadoop cluster does not have access to the internet (offline mode)

   This option initiates a download of files to set up a local repository mirror. A subdirectory called BigMatch is created and RPMs with the associated files are located in directory BigMatch/packages.

5. Offline mode only: Set up a local repository.
   A local repository is required if the Hadoop cluster cannot connect directly to the internet, or if you wish to avoid multiple downloads of the same software when installing services across multiple nodes. In the following steps, the host that performs the repository mirror function is called the repository server. If you do not have an additional Linux host, you can use one of the Hadoop management nodes. The repository server must be accessible over the network by the Hadoop cluster. The repository server requires an HTTP web server.

   Complete the following steps to set up a repository server by using a Linux host with an Apache HTTP server.

   1. On the repository server, if the Apache HTTP server is not installed, install it:

      yum install httpd

   2. On the repository server, ensure the createrepo package is installed.

      yum install createrepo

   3. Ensure there is network access from all nodes in your cluster to the repository server. If data nodes are on a private network and the repository server is external to the Hadoop cluster, you may need to configure iptables for IP forwarding and masquerading.
   4. On the repository server, create a directory for your Big Match repository, such as <mirror web server document root>/repos/BIGMATCH. For example, for Apache httpd, the default is /var/www/html/repos.

      mkdir /var/www/html/repos/BIGMATCH

   5. By selecting Option 2 in step 4, RPMs were downloaded to a subdirectory called BigMatch/packages. Unzip and copy all the RPMs to the mirror web server location, <your.mirror.web.server.document root>/repos/BIGMATCH directory.

      cp BigMatch/packages/bigmatch_binaries/* /var/www/html/repos/BIGMATCH/

   6. Start this web server. If you use Apache httpd, start it by using either of the following commands:

      apachectl start 

      or

      service httpd start

      Ensure that any firewall settings allow inbound HTTP access from your cluster nodes to the mirror web server.

   7. Test your local repository by browsing to the web directory:
      http://<your.mirror.web.server>/repos/BIGMATCH

      You should see all of the files that you copied to the repository server.

   8. On the repository server, run the createrepo command to initialize the repository:

      createrepo /var/www/html/repos/BIGMATCH

   9. In the BigMatch/packages directory, find the RPM to install on the Ambari Server host of the Hadoop cluster: bigmatch-ambari-service-<project_version>-<platform>.rpm

      Then, copy the file to the Ambari Server host and install the RPMs by using the following commands:

      sudo yum localinstall bigmatch-ambari-service-<project_version>-<platform>.rpm

   10. On the Ambari Server node, navigate to the /var/lib/ambari-server/resources/stacks/<stack_name>/<version_number>/repos/repoinfo.xml file. Ensure the <baseurl> elements for the BIGMATCH-some_arch-build_id <repo> entry points to your repository server. Remember, there will be multiple <repo> sections. Make sure that the URL you tested in step 5 g matches exactly the value indicated in the <baseurl> element. For example, the repoinfo.xml might look like the following content after you change http://ibm-open-platform.ibm.com/repos/Bigmatch/ to http://your.mirror.web.server/repos/BIGMATCH:

       <repo> 
       <baseurl> http://<your.mirror.web.server>/repos/BIGMATCH 
       </baseurl>
       <repoid>BIGMATCH-some_arch-build_id</repoid> 
       <reponame>BIGMATCH-some_arch-build_id</reponame>
       </repo>

6. When the module is installed, restart the Ambari server.

   ambari-server restart