The TDI 7.1 installer uses the InstallAnywhere 2009 technology. Before you install, read the following sections and make sure your system meets the minimum requirements.
The IBM TDI 7.1 installer requires 450 MB of temporary disk space during installation, and additionally the following amount of disk space for the TDI components that remain on the computer after installation:
The precise amount of required disk space depends on the components us choose to install; the amounts listed above are applicable for a full Custom option installation. To calculate precisely the necessary disk space, add together the disk space requirements for each component we want to install. See Components in IBM TDI for the required disk space for each TDI component. A default installation generally requires 30MB less than the numbers listed above.
The IBM TDI 7.1 installer requires 512 MB of memory. The precise amount of required memory after installation depends on the components us choose to install.
To calculate the necessary memory requirements, add together the memory requirements for each component we want to install. See Components in IBM TDI for the memory requirements of each TDI component.
Memory requirements for a Typical installation: 484 MB
Memory requirements for a Custom option installation with all components: 868 MB
With some exceptions, the following components are available and selectable for installation as part of IBM TDI 7.1:
More RAM may be required depending on the size and complexity of the solution being created.
IBM TDI does not support the Configuration Editor (CE) on the following operating systems:
Disk space requirements for the Configuration Editor for each supported operating system:
Memory requirements for CE on each supported operating system: 128 MB.
Use the CE Update Site folder to install the TDI Configuration Editor into an existing Eclipse installation. Use the Eclipse software update tool and use this folder as a local update site. The CE update site is only supported for deployment on Eclipse 3.5.1.
IBM TDI does not support the Configuration Editor Update Site on the following operating systems:
CE Update Site requirements are:
Disk space requirements by platform:
Memory requirements: 128 MB (256 MB or more is recommended.)
You must increase memory according to the size of the documentation plug-ins. For example, if the size of the documentation is 100 MB, add at least 80 MB of additional RAM.
If your platform meets these requirements, we can proceed with the download and installation instructions documented in Installing local Help files.
AMC installation into the embedded Web platform requires at least 94 MB or more on each of the following supported operating systems:
Memory requirements: a minimum of 512 MB is recommended.
For the i5/OS platform, the Integrated Web Application Server must already be installed on the target computer. See Installing IBM TDI on i5/OS for details.
Additional components automatically installed that are not selectable:
The JRE used for any of the installed TDI packages is independent of any system-wide JRE or JDK you may have installed on your system. The JRE is installed no matter what features are selected. The uninstaller requires the JRE, so it is always installed.
Disk space requirements by platform:
Memory requirements: Not applicable
The TDI 7.1 License Package contains the license files for TDI.
Disk space requirements by platform:
Note the following differences when installing TDI with administrator as opposed to non-administrator privileges:
RedHat Linux (RHEL) has a security feature known as Security Enhanced Linux or SELinux. SELinux provides security that protects the host from certain types of malicious attacks. A less secure version of SELinux was included in RHEL version 4.0 and was disabled by default, but RHEL version 5.0 defaults SELinux to enabled. The RHEL 5.0 SELinux default settings have been known to prevent Java from running properly. If you try to run the RHEL 5.0 TDI installer, an error resembling the following output may display:
# ./install_tdiv71_linux_x86.bin Initializing Wizard........ Verifying JVM... No Java Runtime Environment (JRE) was found on this system.
The reason for this error is that the Java Runtime Environment (JRE) that InstallAnywhere 2009 extracts to the /tmp directory does not have the required permissions to run. To avoid this error:
We can also edit the /etc/selinux/config configuration file to enable and disable SELinux. The default settings for the /etc/selinux/config file resemble the following lines:
# This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - SELinux is fully disabled. SELINUX=enforcing # SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted
Modifying SELINUX to either SELINUX=permissive or SELINUX=disabled allows the TDI installer to run. However, both modifications of the SELINUX property, to either SELINUX=permissive or to SELINUX=disabled, affect the level of security for the host.
The TDI installer uses a JRE located at install_dir/jvm that cannot run with the SELinux default settings. The installer makes a best effort to avoid the problems with the SELinux default settings by trying to change the TDI JRE security permissions that are blocking the installer. The TDI installer issues a command that changes the security permissions for the TDI JRE so that it can run. The TDI installer issues the following command:
chcon -R -t textrel_shlib_t install_dir/jvm/jre
If the installer cannot issue the chcon command, or if there is an error when issuing the command, edit the permissions manually.
Errors that resemble the following output indicate that the chcon command did not work:
[root@dyn9-37-225-164 V7.1]# ./ibmdisrv Failed to find VM - aborting [root@dyn9-37-225-164 V7.1]# ./ibmditk Failed to find VM - aborting [root@dyn9-37-225-164 V7.1]# bin/amc/start_tdiamc.sh Failed to find VM - aborting
On some UNIX platforms (for example, SLES 10) the Administration and Monitoring Console (AMC) in ISE SE fails consistently to authenticate users, even when correct credentials are specified. Such behavior is observed when AMC is run as a non-root user and the operating system uses a password database (for example, a /etc/shadow file). For more information on this issue, and for a workaround see "Authentication failure on UNIX when LWI runs as non-root user" in IBM TDI V7.1 Problem Determination Guide.