Tivoli Directory Integrator, Version 7.1.1

Before you install

The Tivoli® Directory Integrator 7.1.1 installer uses the InstallAnywhere 2010 technology. Before you install, read the following sections and make sure your system meets the minimum requirements.

Disk space requirements

The IBM® Tivoli Directory Integrator 7.1.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 you 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 you want to install. See Components in IBM Tivoli Directory Integrator for the required disk space for each TDI component. A default installation generally requires 30MB less than the numbers listed above.

Memory requirements

The IBM Tivoli Directory Integrator 7.1.1 installer requires 512 MB of memory. The precise amount of required memory after installation depends on the components you choose to install.

To calculate the necessary memory requirements, add together the memory requirements for each component you want to install. See Components in IBM Tivoli Directory Integrator for the memory requirements of each Tivoli Directory Integrator component.

Memory requirements for a Typical installation: 484 MB

Memory requirements for a Custom option installation with all components: 868 MB

Platform requirements

See Supported platforms

Components in IBM Tivoli Directory Integrator

With some exceptions, the following components are available and selectable for installation as part of IBM Tivoli Directory Integrator 7.1.1:

Runtime Server
A rules engine used to deploy and run Tivoli Directory Integrator integration solutions.
Configuration Editor
A development environment for creating, debugging and enhancing TDI integration solutions.
Note:
IBM Tivoli Directory Integrator does not support the Configuration Editor (CE) on the following operating systems:
  • HP-UX Integrity*
  • Solaris Opteron
  • z/OS
  • i5/OS
  • Linux PPC
  • Linux 390
* On HP-UX Integrity, you have the option of installing the Tivoli Directory Integrator Eclipse CE plug-ins into an existing Eclipse Workbench; see below for more details. If you choose not to do that, and for the other platforms, see Using the Remote Configuration Editor and Using the Remote Configuration Editor on z/OS.

Disk space requirements for the Configuration Editor for each supported operating system:

Memory requirements for CE on each supported operating system: 128 MB.

Configuration Editor Update Site (Eclipse update site for CE)

Use the CE Update Site folder to install the Tivoli Directory Integrator 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.

Note:
IBM Tivoli Directory Integrator does not support the Configuration Editor Update Site on the following operating systems:
  • Solaris Opteron
  • z/OS
  • i5/OS
  • Linux PPC
  • Linux 390
See Using the Remote Configuration Editor and Using the Remote Configuration Editor on z/OS .

CE Update Site requirements are:

Java API documentation
Full HTML documentation of TDI internals. Essential reference material for scripting in solutions, as well as for developing custom components.
Examples
A series of short, illustrative example Configs that highlight specific Tivoli Directory Integrator features or components.
Help system, v3.3.1 (Host TDI help locally. The default is online.)
You can install an IBM User Interface Help System built on Eclipse (formerly known as IBM Eclipse Help System, or IEHS) locally as an alternative to using the global online help service. This option requires manual download and deployment of the Tivoli Directory Integrator help files after installation.

Disk space requirements by platform:

Memory requirements: 128 MB (256 MB or more is recommended.)

Note:
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, you can proceed with the download and installation instructions documented in Installing local Help files.

embedded Web platform (includes Integrated Solutions Console SE) v8.1.0.3
Tivoli Directory Integrator includes an embedded lightweight Web server platform, sometimes referred to as "LWI". This server platform is based on the Eclipse and Open Services Gateway Initiative (OSGI) architecture and supports running web applications and Web services. The runtime provides a secure infrastructure with a small footprint and minimal configuration. The embedded Web platform includes Integrated Solution Console SE, which is used as the default alternative for deploying AMC on an existing ISC installation. The embedded Web platform provides an OSGI based lightweight infrastructure for hosting Web applications and Web services with the following characteristics:

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.

Note:
For the i5/OS® platform, the Integrated Web Application Server must already be installed on the target computer. See Installing IBM Tivoli Directory Integrator on i5/OS for details.
AMC: Administration and Monitoring Console
A browser-based application for monitoring and managing running Tivoli Directory Integrator Servers. AMC runs in the Integrated Solutions Console (ISC). In previous releases, AMC was a servlet application that was deployed into an embedded or existing instance of WebSphere Application Server (WAS). Tivoli Directory Integrator 7.1.1 supports ISC SE 7.2.0.2 and Tivoli Integrated Portal 2.1 (ISC embedded).

Additional components automatically installed that are not selectable:

JRE (Java Runtime Environment) 6.0 SR9
A subset of the Java Development Kit (JDK) that contains the core executable files and other files that constitute the standard Java platform. The JRE includes the Java Virtual Machine (JVM), core classes, and supporting files.
Note:
The JRE used for any of the installed Tivoli Directory Integrator 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

Password Synchronization Plug-ins
All supported platforms: 8 MB
Miscellaneous
Contains the License Package, the Uninstaller, the Update Installer and Tivoli Directory Integrator overhead.

The Tivoli Directory Integrator 7.1.1 License Package contains the license files for Tivoli Directory Integrator.

Disk space requirements by platform:

Memory requirements: Not applicable.

Other requirements

Root or Administrator Privileges

Note the following differences when installing Tivoli Directory Integrator with administrator as opposed to non-administrator privileges:

Security Enhanced (SELinux)

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 Tivoli Directory Integrator installer, an error resembling the following output may display:

# ./install_tdiv711_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 2010 extracts to the /tmp directory does not have the required permissions to run. To avoid this error:

  1. Disable SELinux: setenforce 0.
  2. Run the Tivoli Directory Integrator installer.
  3. Enable SELinux again: setenforce 1.

You 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 Tivoli Directory Integrator 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 Tivoli Directory Integrator 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 Tivoli Directory Integrator JRE security permissions that are blocking the installer. The Tivoli Directory Integrator installer issues a command that changes the security permissions for the Tivoli Directory Integrator JRE so that it can run. The Tivoli Directory Integrator installer issues the following command:

chcon -R -t textrel_shlib_t install_dir/jvm/jre
Note:
If the installer cannot issue the chcon command, or if there is an error when issuing the command, you must 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.1]# ./ibmdisrv 
Failed to find VM - aborting 

[root@dyn9-37-225-164 V7.1.1]# ./ibmditk
Failed to find VM - aborting

[root@dyn9-37-225-164 V7.1.1]# bin/amc/start_tdiamc.sh
Failed to find VM - aborting

Authentication of AMC on Unix/Linux

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 Tivoli Directory Integrator V7.1.1 Problem Determination Guide.

[ Top of Page | Previous Page | Next Page | Contents | Terms of use | Feedback ]
(C) Copyright IBM Corporation, 2003, 2012. All Rights Reserved.
IBM Tivoli Directory Integrator 7.1.1