Installing Big Match on Ambari (V11.5.0.5 and above)

Download the InfoSphere® Big Match for Hadoop installation artifacts and run the installation setup for the node on a machine that has internet access.

1. Extract the installation asset that you downloaded from Passport Advantage.

   tar -tzvf IBM_INFOSPHERE_BIG_MATCH_FOR_HADO.tar.gz

   The asset's contents are as follows:

   • bigmatch_binaries/bigmatch-ambari-service-11.5.0.11-ambari-common.rpm
   • bigmatch_binaries/bigmatch-ambari-service-11.5.0.11-hdp-3.1.rpm
   • bigmatch_binaries/bigmatch-rpm-11.5.0.11.rpm
   • bigmatch_binaries/BIGMATCH-GPG-KEY.public
   • bigmatch_binaries/bigmatch-native-rpm-11.5.0.11-x86_64.rpm
   • bigmatch_binaries/bigmatch-ambari-service-11.5.0.11-hdp-2.6.rpm
   • bigmatch_binaries/bigmatch-native-rpm-11.5.0.11-ppc64le.rpm
2. Set up a local repository.
   A local repository is required. 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. When you extracted the installation assets, RPM files were placed to a subdirectory called bigmatch_binaries. 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 the 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 RPMs to install on the Ambari Server host of the Hadoop cluster: bigmatch-ambari-service-<project_version>-<platform>.rpm
      For example:

      bigmatch-ambari-service-11.5.0.11-ambari-common.rpm
      bigmatch-ambari-service-11.5.0.11-hdp-2.6.rpm
      bigmatch-ambari-service-11.5.0.11-hdp-3.1.rpm

      Then, copy the files to the Ambari Server host and install the RPMs by using the following commands (replace <product-version> with the Big Match version):

      sudo yum localinstall bigmatch-ambari-service-<product-version>-ambari-common.rpm
      sudo yum localinstall bigmatch-ambari-service-<product-version>-hdp-2.6.rpm
      sudo yum localinstall bigmatch-ambari-service-<product-version>-hdp-3.1.rpm

   10. On the Ambari Server node, navigate to and edit the repoinfo.xml file for the Big Match service.
       Tip: In Big Match version 11.5.0.11 and above, repoinfo.xml is located in /var/lib/ambari-server/resources/stacks/<stack_name>/<version_number>/services/BIGMATCH/repos/. In version 11.5.0.10 and below, it is located in /var/lib/ambari-server/resources/stacks/<stack_name>/<version_number>/repos/repoinfo.xml.

       Ensure the <baseurl> elements for the BIGMATCH-some_arch-build_id <repo> entry point to your repository server. Remember, there will be multiple <repo> sections. Make sure that the URL you tested in step 5g exactly matches the value indicated in the <baseurl> element.

       For example, the repoinfo.xml file might look like the following 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>

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

   ambari-server restart