Install Java installer

The Java Installer installs Data Integration on UNIX, Linux, and IBM i platforms.

The install procedure does the following:

Gathers input describing where to install and information about the host environment.
Verifies information gathered in Step 1 before copying any files:
- The version of the Java Run-time Environment must be at a level acceptable for the Data Integration executable processes.
- The Java compiler should be available wherever Data Integration is installed.
You receive a warning if the javac file is not available. The install can continue without javac, but expressions and join tables will not function.
- The TCP/IP port number chosen for use by the Listener V5.8 must be available and not used or reserved by any other service.
Configures shell scripts using input gathered in Step 1.
Installs the files.
This involves copying components from the source location to the user-chosen target directory on the host.
On UNIX and Linux platforms, configures the host so that Listener starts at host boot or IPL. This is an optional feature; the user can choose to do this or not.
Starts the Listener.
Saves the install configuration. This step creates a properties file in the target install directory with the file name of the host being installed and a file extension of ini. This file contains the parameters values chosen for this host install. Along with the log file created during the install, this file serves as a record of the install. Subsequent runs of the Installer attempt to locate this file.

Install Modes

The install may be a full install or a reconfiguration of an existing install. The install may be local or remote, and may be done in batch or interactive mode.

Full or Reconfiguration
Full install is a complete install of all files.
Once Data Integration has been installed, Reconfiguration is offered as a choice for changing all parameters except the install directory and the host where it is installed.
Local or Remote

There are two types of hosts during an install. The originating host runs the installer program. The recipient host is the machine on which Data Integration is being installed.

A local install runs the Installer on the originating host and installs Data Integration on the same host. In this case, the originating host and recipient host are the same.
A remote install runs the installer on the originating host but installs Data Integration onto a different host. The Java Installer may run on a Windows or UNIX host and install on a UNIX, Linux, or IBM i host. The TCP/IP server daemons, FTP and SSH, must be running on the installing host.
Interactive GUI or Batch Installer

Data Integration may be installed via a GUI Installer or a Batch Installer.

Java 8 or higher is required to be installed on the remote system.

Installer Support by Platform

Listed below are the platforms upon which Data Integration may be installed using the Java Installer:


OperatingSystem	Install Data Integration Locally	Install Data Integration Remotely
UNIX	Use the GUI Installer or the Batch Installer.	From another UNIX or Linux host or a Windows host, use either the GUI Installer or the Batch Installer.
Linux	Use the GUI Installer or the Batch Installer.	From another UNIX host or a Windows, use either the GUI Installer or the Batch Installer.

Install Files

The install files, listed below, are packaged together in one file, named install.zip. To list the contents of install.zip without unpacking, enter the following command:

jar tvf install.zip


File	Description
binstaller.cmd	.bat file that runs the Batch Installer on Windows
binstaller.sh	Shell script that runs the Batch Installer on UNIX or Linux
ginstaller.cmd	.bat file that runs the GUI Installer on Windows
ginstaller.sh	Shell script that runs the GUI Installer on UNIX or Linux
inetfactory.jar	Library, provided by jScape, required for install networking tasks and for installing the Listener start and kill scripts in the boot area
installer.jar	Java Installer program for both the GUI and Batch Installer programs
jsch-0.1.54.jar	Library used for SSH secure connections
jt400.jar	Library from IBM required for FTP install tasks and running Data Integration after it is installed. Contains the IBM i JDBC driver.
JT400offbox.properties	File used to enable remote hosting.
JTOpen400.properties	File used to enable FOR BIT DATA (IBM i Only) translation to treat binary data values as character values
log4j-1.2.8. jar	Library used for writing messages to an install log
omni.zip	Data Integration packaged into a zip file
udbcs.zip	Files containing UDB Change Selector

Install

Do the following to install:

Copy the install.zip from the download to a writable directory on the originating host where the Installer is to be run. When FTPing install.zip across a network, do a BINARY transfer of the file.

Unpack the install files (listed above) on the installing host. The command to unpack depends on the platform of the originating host.

On a UNIX platform, issue the command:

jar xvf install.zip

The Installer does not work correctly if the following characters are used in any UNIX file or directory names processed by the Installer:


blank space	;	\	(	)	\|
@	!	#	$	&	<
>	?	*	{	}	^
tab character	new line character	“double quote	' single quote

On a Windows platform, use WinZip or another similar program or the following command:

jar xvf install.zip

Run the GUI or Batch Installer.

Note: The GUI installer does not support install Kafka and Db2 for z/OS installs. Use the batch installer to connect to Kafka or Db2 for z/OS.

Run the GUI Installer

The GUI Installer may perform the install on the following:

Local host running UNIX or Linux.
Remote machine running UNIX and Linux, where the local machine runs UNIX, Linux, or Windows.

When the originating host is UNIX, run the GUI installer with the command:

sh ginstaller.sh

When the originating host is Windows, run the command:

ginstaller.cmd

The GUI Installer may be used to perform an initial full install of Data Integration, or a reconfiguration of an existing install. During a reconfiguration, any value may be changed, even though the values fill in with information from the previous install.

Note the following:

Before doing a reconfiguration, shut down Listener.
If you are upgrading, you should recommit your model when you finish the install to take advantage of the latest features of the new release.

Note: Description of the GUI windows and the information requested for installing Data Integration follow. The appearance of the window varies slightly depending on the platform.

Run the Batch Installer

The Batch Installer may perform the install on a local host running UNIX and Linux. The Batch Installer may perform the install on a remote machine running UNIX and Linux and the local machine is UNIX or Windows.

The Batch Installer may be used to perform an initial full install of Data Integration or a reconfiguration of an existing install.

Important: Before doing a reconfiguration, shut down Listener.

Batch installer Steps

To run the batch installer, do the following, as described in the associated sub-section:

Create the host.list file containing entries for installing to one or more hosts.
Create the <host_name>.properties file for each host listed in the host.list file where HOSTNAME is the name of the host machine to install Data Integration.
Run the batch installer.
If you are installing on a server using Oracle, create the config. properties file.

Create the host.list File

The host.list file identifies one or more hosts on which to install Data Integration. It must be located in the current directory where the Installer is running. Below is a sample host.list file:

remote=Nreconfigure=Nvector=UNIXremote=Yreconfigure=Ymountain=UNIX

This example asks the Batch Installer to install on two hosts:

A local, initial full install onto the UNIX host named vector
A remote, reconfigure install onto the UNIX host named mountain

Keywords and input parameters may be in mixed case. The order of the input parameters is important. Comments are denoted by a # in the first column of a line. Comments are not allowed on the right side of a key=value property specification.


Keyword or Input Parameter	Description
Remote	One of the following: N is the default. N indicates the install will occur locally where the Installer program is running. Y indicates the Installer program will install on a different host than where the installer is running. The originating host is a different host machine than the recipient host. This remote keyword affects all installing hosts defined later in the host.list file until another remote keyword is specified.
Reconfigure	One of the following: N is the default. N indicates the installer must perform a full install of Data Integration. Y indicates that hosts have an existing Data Integration install and should be reconfigured. This reconfigure keyword affects all hosts defined later in the host.list file until another reconfigure keyword is specified.
host_filename = HOST_TYPE	Defines host (recipient host) on which to install Data Integration. host_filename–Identifies the properties file containing the install parameters for installing to one host. host_filename plus.properties comprises the properties filename. In the example above, there would be two property files names named vector.properties and mountain.properties. HOST_TYPE–The operating system type of the recipient host. The valid operating system type is UNIX. (Use UNIX for Linux.)