Reporting with Hadoop - Big Data Made Easy: A Working Guide to the Complete Hadoop Toolset - page 337

Having extracted the JavaJDK, I use the Linux su (switch user) command to change to the root account and move
the software to /usr/local/. The Linux mv (move) command moves the jdk1.8.0_25 directory. The Linux cd (change
directory) command moves to the /usr/local/ directory. The Linux chown (change owner) command recursively
changes the ownership of the Java release to the Linux hadoop account. Finally, the export command sets the
JAVA_HOME variable to the path of this new Java release:
[hadoop@hc1nn Downloads]$ su -
Password:
[root@hc1nn ~]# cd /home/hadoop/Downloads
[root@hc1nn Downloads]# mv jdk1.8.0_25 /usr/local
[root@hc1nn Downloads]# cd /usr/local
[root@hc1nn local]# chown -R hadoop:hadoop jdk1.8.0_25
[root@hc1nn local]# export JAVA_HOME=/usr/local/jdk1.8.0_25
It is this Oracle Sun JavaJDK that the Talend release requires, so with the JAVA_HOME variable set I can attempt to
install the software. As the root user, I change the directory to the Downloads directory and then change the directory
to the directory containing the unpacked Talend software. After that, I run the non-64 bit linux.run file. The ./
prepended to the name specifies that the installation file will be sourced from the current directory:
[root@hc1nn local]# cd /home/hadoop/Downloads
[root@hc1nn Downloads]# cd TalendTools-5.5.1-cdrom
[root@hc1nn TalendTools-5.5.1-cdrom]#
./Talend-Tools-Installer-r118616-V5.5.1-linux-installer.run
The installation is simple. I just accept all defaults and install only the client application, not the server, as the
server is not required for this example. As mentioned earlier, I also need a platform-enabled license file supplied by
Talend to enable the profiling function. This file is specified during the installation. I install the software to the default
path /opt.
The Talend application also needs an rpm build packaging component; the yum installation command, run as
root, installs the necessary software, as follows:
[root@hc1nn TalendTools-5.5.1-cdrom]# yum install rpm-build
Finally, the Talend client software can be started from the studio subdirectory of the Talend software installation
directory /opt/TalendTools-5.5.1. The 5.5.1 string shows the version of the Talend Enterprise software that has been
installed. The list obtained using the Linux ls command shows that there are numerous Linux .sh and windows .ini
files available for starting Talend. Given that I have installed Talend on a 32-bit Linux host, however, the .sh file has
“linux” in its name but lacks the “64,” which denotes a 64-bit architecture. The ./ in the final command indicates that
the file should be run from the current directory. The “and” character ( & ) denotes the command should be run in the
background:
[root@hc1nn TalendTools-5.5.1-cdrom]# cd /opt/TalendTools-5.5.1/studio/
[root@hc1nn studio]# ls *.sh *.ini