Installing the IBM Big SQL package

After you have prepared the environment and acquired the software, follow these steps to install IBM Big SQL.

Before you begin

Ensure that you installed Hortonworks Data Platform (HDP) (if performing a fresh install rather than a migration).
Ensure that you followed the steps in Preparing to install IBM Big SQL.
You must have acquired the software from Passport Advantage download website. See Obtaining IBM Big SQL for details.
When you install Big SQL as the non-root user, preface the instructions with sudo, where the instruction would normally require the root user. For more information about non-root access, see Configuring Ambari agents for non-root access to IBM Big SQL.

About this task

When you run the ibmbigsql_5.0.1.bin file, configuration files are copied to appropriate locations to enable Ambari to see the services as available. When adding services through Ambari, additional software packages can be downloaded. If the Hadoop cluster cannot directly access the internet, a local mirror repository can be created.

Where you perform the following steps depends on whether the Hadoop cluster has direct internet access.

If the Hadoop cluster has direct access to the internet, perform the steps from the Ambari server of the Hadoop cluster.
If the Hadoop cluster does not have direct internet access, perform the steps from a Linux host with direct internet access. Then, transfer the files, as required, to a local repository mirror.

Procedure

Update the permissions on the downloaded .bin file to enable execute.
```
chmod +x ibmbigsql_5.0.1.bin
```
Run the .bin file to extract and install the services in the module.
Navigate to the directory that contains the bin file and run
```
./ibmbigsql_5.0.1.bin
```
If you are running the bin file as a non-root user, ensure that the non-root user has the required sudo privileges.
After the prompt, agree to the License terms. Reply yes | y to continue with the install.
You are prompted to answer several questions regarding your installation method, system architecture, and operating system version.

Set up a local repository for an offline install (optional).

If you chose to do a offline installation in Step 4, you must set up a local repository. Otherwise you can skip this step.

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. The following instructions describe how to set up a repository server by using a Linux host with an Apache HTTP server.

On the repository server, if the Apache HTTP server is not installed, install it:
```
yum install httpd
```
On the repository server, ensure that the createrepo package is installed.
```
yum install createrepo
```
Make sure 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 might need to configure iptables.
On the repository server, create a directory for your Big SQL repository, such as <mirror web server document root>/repos/bigsql. For example, for Apache httpd, the default is /var/www/html/repos.
```
mkdir -p /var/www/html/repos/bigsql
```
Step 2 above downloads the RPMs to the subdirectory IBM-Big_SQL/packages/IBM-Big_SQL/<OS><version>/<platform>/<BigSQL_version>/.... Copy all of the RPMs to the mirror web server location, <your.mirror.web.server.document root>/repos/bigsql directory.
For example, the command for version 5.0.1 using RHEL7 is:
```
sudo cp -r <download directory path>/IBM-Big_SQL/packages/IBM-Big_SQL/RHEL7/x86_64/5.0.1.0/* /var/www/html/repos/bigsql/
```
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.
Test your local repository by browsing to the web directory:
```
http://<your.mirror.web.server>/repos/bigsql
```
You should see all of the files that you copied to the repository server.
On the repository server, run the createrepo command to initialize the repository:
```
createrepo /var/www/html/repos/bigsql
```

In the /var/www/html/repos/bigsql directory, find the RPM to install on the Ambari Server host of the Hadoop cluster:

BigSQL

Operating system	File name
Red Hat Enterprise Linux® v6 on x86-64 (RHEL6)	IBM-Big_SQL-5_0_1_0.el6.x86_64.rpm
Red Hat Enterprise Linux v7 on x86-64 (RHEL7)	IBM-Big_SQL-5_0_1_0.el7.x86_64.rpm
Red Hat Enterprise Linux on Power Systems	IBM-Big_SQL-5_0_1_0.el7.ppc64le.rpm

Then, copy the file to the Ambari Server host and install the RPM by using the following command:

yum install <BigSQL_RPM>.rpm

or if you are running as a non-root user:

sudo yum install <BigSQL_RPM>.rpm

If you later find errors in the configuration file, make your corrections and then run the command:
```
yum clean all
```

Make the following changes to /var/lib/ambari-server/resources/extensions/IBM-Big_SQL/5.0.1.0/services/BIGSQL/repos/repoinfo.xml and restart the Ambari server.

<repo>
  <baseurl>http://<local repo server fully qualified domain name>/repos/bigsql</baseurl>
  <repoid>IBM-Big_SQL-5_0_1_0</repoid>
  <reponame>IBM-Big_SQL-5_0_1_0</reponame>
  </repo>

If you are not running Big SQL on HDP version 2.5, you can skip this step. If you are running on HDP 2.5, proceed with these steps. On the Ambari server host, check that the BIGSQL symlink is not in /var/lib/ambari-server/resources/stacks/HDP/2.5/services/BIGSQL, pointing to itself. This step can be achieved with the following command as root:
```
unlink /var/lib/ambari-server/resources/stacks/HDP/2.5/services/BIGSQL/BIGSQL
```
If the command is successful, no output is provided. If the symlink does NOT exist, the command fails with the following error message:
```
unlink: cannot unlink ‘/var/lib/ambari-server/resources/stacks/HDP/2.5/services/BIGSQL/BIGSQL’: No such file or directory
```
This error message is the desired outcome so it can be safely ignored.

Example

This is an example of running the Big SQL module for OFFLINE installation:


[root@main1 DownloadDirector]# ./ibmbigsql_5.0.1.bin
Creating directory ./IBM-Big_SQL
Verifying archive integrity... All good.
Uncompressing IBM-Big_SQL  100%
************************************************************************
License Files
************************************************************************
License files are available in the directory:
/opt/builds/ambari/IBM-Big_SQL/licenses

1. Do you Accept the Terms and Conditions in the Licenses Directory? (y/n) : y

************************************************************************
Migration from IOP to HDP
************************************************************************
2. Are you migrating from IOP to HDP? YES(1) or NO(2) : 1

************************************************************************
 The IOP directory /usr/iop exists, so you currently have IOP installed.
************************************************************************

************************************************************************
Installation Method (Online/Offline)
For ONLINE, make sure you have the package lsb-release installed.
Run the cmd --> sudo yum install redhat-lsb-core
************************************************************************
3. Do you wish to use the ONLINE(1) or OFFLINE(2) method? 2

************************************************************************
Remember to have HDP installed.
************************************************************************

************************************************************************
Current System's Architecture
************************************************************************
You are running on: x86_64

************************************************************************
Target System's Architecture
************************************************************************
4. Is the system to be installed on x86_64(1) or ppc64le(2)? : 1

************************************************************************
Current System's RHEL version
************************************************************************
You are running: Red Hat Enterprise Linux Server release 7.2 (Maipo)

************************************************************************
Target System's RHEL version
************************************************************************
5. Is the system to be installed on using RHEL 6 or 7? (6/7): 7

************************************************************************
Executing BIN File
************************************************************************

You chose  OFFLINE + HDP
Downloading...
Installing Package...
...
Installation Complete

What to do next

Enable the Big SQL Extension, select the service that you want to install and deploy. Even though your module might contain multiple services, install the specific service that you want. Installing one service at a time is recommended. Follow the service specific installation instructions for more information.