Installing IBM Tivoli Directory Integrator

The Tivoli® Directory Integrator installer allows you to install Tivoli Directory Integrator 7.1.1 in its entirety, only those Tivoli Directory Integrator components that you need, upgrade a previous version of Tivoli Directory Integrator (versions 6.0, 6.1, 6.1.1, 7.0, or 7.1), or add features to an existing Tivoli Directory Integrator 7.1.1 installation.

Installing Tivoli Directory Integrator 7.1.1 uninstalls a previous version; the uninstallation does not remove any files that the user has created. User created files are still available after the new installation completes. Configuration files such as global.properties and am_config.properties are migrated to Tivoli Directory Integrator 7.1.1, keeping any custom configuration changes that have been made. The Tivoli Directory Integrator 7.1.1 installation continues to use the features available in previous versions of Tivoli Directory Integrator:

• Administration and Monitoring Console (AMC)
• Configuration Editor (CE)
• Examples
• IBM User Interface Help System built on Eclipse
• Java API Documentation
• Runtime Server

Launching the appropriate installer

You can launch the IBM Tivoli Directory Integrator 7.1.1 Installer by using one of the following methods:

Launch the installer from the Launchpad

The Tivoli Directory Integrator Launchpad provides essential getting started installation information and links to more detailed information on various installation, migration, and post installation topics. In addition, Launchpad allows you to launch the Tivoli Directory Integrator installer.

Notes:

1. The Launchpad is not available on z/OS® and i5/OS®.
2. Using the Launchpad requires that you have a supported Web browser installed and configured; if this is not the case, you cannot use the Launchpad. However, you can still use the platform-specific installer directly; see Using the platform-specific TDI installer for instructions on how to use theTivoli Directory Integrator Installer.

Note:

1. Open the Tivoli Directory Integrator Launchpad by typing the following command at the command prompt:
   • For Windows platforms, type:

     Launchpad.bat

   • For all other platforms, type:

     Launchpad.sh

   The menu on the left of the Launchpad allows you to navigate the Launchpad windows. Click a menu item to view information about it. The following menu items are available:

   Welcome

   The installation Welcome window contains links to:

   • IBM Tivoli Directory IntegratorWeb site
   • 7.1.1 Documentation
   • Support Web site
   • Tivoli Directory Integrator news group

   

   The following options on the left are Tivoli Directory Integrator Launchpad windows:

   Release Information

   This window contains a list of some of the new and improved features available this release, as well as links to documentation about the release.

   Prerequisite Information

   This window contains links to information about platform support and hardware requirements.

   Installation scenarios

   This window contains a description of the TDI components available for installation. You can install some or all of these components during installation. This window also contains a description of the Password Synchronization Plug-ins components available for installation.

   Migration Information

   This window contains a link to information about migrating from Tivoli Directory Integrator 6.0, 6.1.X, 7.0, or 7.1 to 7.1.1. It also contains information about migrating the Derby System Store.

   Install IBM Tivoli Directory Integrator

   This window contains links to the IBM Tivoli Directory Integrator Installer, as well as links to installation, migration and supported platforms documentation. See Using the platform-specific TDI installer for instructions on how to use the IBM Tivoli Directory Integrator Installer.

   Install IBM Tivoli Directory Integrator Password Synchronization Plug-ins

   This window contains links to the IBM Tivoli Directory Integrator Password Synchronizer Plug-ins Installer, as well as links to installation and supported platforms documentation.

   Note:

   This window is not available on Linux PPC and Linux 390 platforms.

   Exit

   Exits the Launchpad, without installing anything.

2. On the installation window, click IBM Tivoli Directory Integrator Installer. This launches the installer. See Using the platform-specific TDI installer for instructions on how to use the installer.

Launch the installer directly

You can launch the installer directly using the installation executable file:

1. Locate the installation executable file for your platform in the tdi_installer directory on the product CD (on i5/OS this directory is called TDI_INST).

   Windows Intel

   install_tdiv711_win_x86.exe

   Windows 64-bit

   install_tdiv711_win_x86_64.exe

   AIX

   install_tdiv711_aix_ppc.bin

   AIX 64-bit

   install_tdiv711_aix_ppc_64.bin

   Linux

   install_tdiv711_linux_x86.bin

   Linux 64-bit

   install_tdiv711_linux_x86_64.bin

   Power PC Linux

   install_tdiv711_ppclinux.bin

   z/OS Linux

   install_tdiv711_zlinux.bin

   Solaris Sparc

   install_tdiv711_solaris_sparc.bin

   Solaris (Intel)

   install_tdiv711_solaris_x86_64.bin

   HP-UX Integrity

   install_tdiv711_hpux_ia64.bin

   i5/OS

   INST_TDI.SH

2. Double-click the executable file, or type the executable file name at the command prompt. This launches the installer. See Using the platform-specific TDI installer for information on how to use the installer.

Once you have launched the installer (using the Launchpad or by starting the platform-dependent installer directly), you are ready to begin the process of Using the platform-specific TDI installer.

Using the platform-specific TDI installer

The platform-specific Tivoli Directory Integrator installer is launched either form the Launchpad or from the command line. The Tivoli Directory Integrator installer can be used to install a new copy of Tivoli Directory Integrator, add a feature to an existing instance of Tivoli Directory Integrator, or upgrade a previous version of Tivoli Directory Integrator. The default install location on your computer for Tivoli Directory Integrator varies with the platform.

During installation, the Installer will log its actions in files residing in the system’s temporary files directory, typically /tmp or /var/tmp on UNIX platforms.

Before you install

Installing IBM Tivoli Directory Integrator on i5/OS

Tivoli Directory Integrator supports installation on i5/OS. The i5/OS platform does not support a GUI interface (Launchpad). i5/OS supports the command line installation -console option. See Installing using the command line.

The following Tivoli Directory Integrator features are not available on i5/OS, and are not listed as installable features during -console installation:

• Configuration Editor (CE/Integrated Development Environment (IDE)) - This component is the Tivoli Directory Integrator IDE. Also see Using the Remote Configuration Editor on z/OS.
• Configuration Editor Update Site (Eclipse Update site for CE) - An Eclipse update site used for CE maintenance and for allowing the customer to install the CE to an existing Eclipse workbench if they do not want to use the stand alone Rich Client Platform (RCP) application.

Prior to installing Tivoli Directory Integrator, certain software must already be installed on the i5/OS operating system running Tivoli Directory Integrator.

PTF versions

For i5/OS V6R1 the installer will check that the following items are installed:

1. Product 5761JV1 option 11 (J2SE 6.0 32 bit)
2. PTF group SF99562 level 19 or higher (Java)
3. Product 5761DG1, *BASE (IBM HTTP Server for i5/OS - contains LWI 8.1.0.3)
4. PTF group SF99115 is at level 18 or higher (LWI, AMC Role and SSL Fix)

For i5/OS V7R1 the installer will check that the following items are installed:

1. Product 5761JV1 option 11 is installed (J2SE 6.0 32 bit)
2. PTF group SF99572 is at level 08 or higher (Java)
3. Product 5770DG1, *BASE is installed (IBM HTTP Server for i5/OS - contains LWI 8.1.0.3)
4. PTF group SF99368 is at level 07 or higher (LWI, AMC Role and SSL Fix)

Java virtual machine version

Tivoli Directory Integrator requires the IBM J9 32-bit JVM on all versions of i5/OS. If the J9 32-bit JVM is not found or if not having minimum PTF group level, the following error message is displayed:

The install was unable to detect the IBM J9 VM (32-bit). The IBM J9 VM is required for this product. 
Please install this JVM then try again.

If you see this message, cancel the installation, install the IBM J9 VM, and begin the installation again.

If you choose the embedded Web platform feature, the install verifies to ensure that LWI 8.1.0.3 (v7r1 or v6r1) is resident on the target system.

If the PTFs or products are not found, the following error message is displayed:

The installer was unable to detect the i5/OS product/PTFs required by the embedded Web platform feature. 
You may choose to continue the install without the embedded Web platform feature or you may exit now and 
refer to the install log for a list of the missing requirements.

Installation

To begin installing on i5/OS:

1. Locate the installation executable file for i5/OS in the TDI_INST directory on the product CD. Launchpad is not available on i5/OS. The default location to install i5/OS on your computer is: /QIBM/ProdData/IBM/TDI/V7.1.1
2. On i5/OS, in order to extract the Tivoli Directory Integrator 7.1.1 installer from a TAR image, you must set environment variable "QIBM_CCSID" to 819; that is, run the command

   export QIBM_CCSID=819

   before un-tarring the Tivoli Directory Integrator installer TAR image.

Another i5/OS difference is on the Tivoli Directory Integrator Solutions directory panel. On i5/OS, there is a specific place for user data. As a result, instead of giving you the option to make the installation directory the same as the solutions directory, the option reads: Use the TDI User Product Directory.

Installing using the graphical installer

Install Panel flow

Pre-Initialization Panel

You invoke the installer executable either from the command line, or by double clicking the executable (Windows only). This panel will initially appear followed by a splash screen:

Note:

The splashscreen may also show a drop down list of language choices if the underlying system supports more than one. (The default is English.)

The Welcome Panel

This is the Welcome Panel for the installer. This is the default panel provided by the InstallAnywhere installer. You have the option to continue by hitting the Next button or canceling out of the installer by pressing Cancel.

J9 PTF Missing Panel (i5/OS only)

On i5/OS, the TDI install will check to make sure the IBM J9 32bit JVM is installed. If this JVM is not found, an error message will be displayed:

The install was unable to detect the IBM J9 VM (32-bit).  
The IBM J9 VM is required for this product.  Please install this JVM then try again.

You will need to cancel the install at this point. This panel is not shown if the JRE check passes.

Previous Installed TDI Information Panel

This panel informs your that detecting previous versions of TDI may take some time.

If a previous version is detected, you are presented with a number of upgrade options.

The License Panel

The License Panel is provided by the IBM license tool. This panel will be shown in a New TDI v711 install and Upgrading an older TDI version.

Destination Panel

Notes:

1. This panel will not be shown if an upgrade from TDI 6.0, TDI 6.1, TDI 6.1.1, TDI 7.0, or TDI 7.1 was selected nor will it be shown if you are adding features to an existing TDI 7.1.1 instance.
2. The destination panel will have the last value entered if you go forward in the wizard to other panels and then come back.
3. Non-ASCII characters and the following list of characters are not supported in the install path: ";|*?!#&$',=^@%+

Install Type Panel

The Typical install includes the Runtime Server, the Configuration Editor (CE), Javadocs, Examples and AMC. It does not include the Configuration Editor Update Site, IBM User Interface Help System built on Eclipse, or the Password Synchronization Plug-ins.

If you select Typical, the feature selection panel is skipped. Also, you will automatically get the bundled embedded Web platform/ISC package. The ISC Directory panel will be skipped.

Feature Selection Panel

This panel lets you specify which features will be installed. Any feature can be individually installed if needed. The only exception to this is that if the Configuration Editor is selected, the server will be selected because the Configuration Editor is a subfeature of the server.

If any feature is not supported on the platform it will not be shown on the feature selection panel.

Note:

The Configuration Editor feature is not available on zLinux, Linux PPC, Solaris Opteron, HP IA64 or i5/OS. The Configuration Editor Update Site feature is not available on zLinux, Linux PPC, Solaris Opteron, or i5/OS. The Password Synchronization Plug-ins feature is not available in the General Purpose edition nor on zLinux, Linux PPC, Solaris Opteron , HP-UX IA64 or i5/OS.

The following list summarizes each feature:

Runtime Server

A rules engine used to deploy and run TDI integration solutions.

Configuration Editor

A development environment for creating, debugging and enhancing TDI integration solutions. (Not available on zLinux, Linux PPC, Solaris Opteron, HP-UX or i5/OS.) This feature can not be installed without installing the Runtime Server.

Configuration Editor Update Site

Patterned after the Eclipse Update Site. Contains the necessary files to install the Config Editor to an existing Eclipse. It will also be used for maintenance. (Not available on zLinux, Linux PPC, Solaris Opteron or i5/OS.)

Javadocs

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 TDI features or components.

IBM User Interface Help System built on Eclipse, v3.3.1 (local help)

An IBM User Interface Help System (previously known as IEHS) built on Eclipse that you can install locally as an alternative to using the global online help service. This option requires manual download and deployment of Tivoli Directory Integrator help files after installation.

embedded web platform

The embedded Web platform 8.1 package; this version includes ISC SE.

Administration and Monitoring Console

A browser-based application for monitoring and managing running Tivoli Directory Integrator Servers.

Password Synchronization Plug-ins

TDI password synchronization plug-ins. (Not available in the General Purpose edition nor on zLinux, Linux PPC, Solaris Opteron , HP-UX or i5/OS.

Missing embedded web platform pre-req Panel (i5/OS only)

If the installer is missing the embedded web platform pre-requisites on i5OS and the embedded web platform feature is chosen (either by selecting it on the custom feature panel or by choosing a typical install), it will display the message:

The installer was unable to detect the i5/OS product/PTFs required by the embedded web platform feature.  
You may choose to continue the install without the embedded web platform feature or you may exit now 
and refer to the install log for a list of missing requirements.

You can choose to go back and deselect the embedded web platform feature through the custom feature panel and continue, or to exit the installer and get the appropriate products installed.

TDI Solutions Directory Panel

This panel is only displayed if the Server feature was chosen. It lets the user decide where the default Solution Directory the Server and Configuration Editor will search under. The Solution Directory is a static directory containing the solutions created by the user that will be run. By default, this panel will select to have the Solution Directory set the user's home directory.

From TDI 7.1.1 onwards, for Windows and UNIX platforms, if you select the Select a directory to use radio button, you need to specify a valid Solution Directory. The Universal Naming Convention (UNC) path is supported for Solution Directory during installation time.

On i5/OS (console only), the Use Install Directory will be replaced with Use the TDI User Product Directory. The i5/OS platform has a specific location (/QIBM/UserData) for user data. The install directory is not appropriate.

Note:

This panel will not be shown in an upgrade from TDI 6.0, TDI 6.1, TDI 6.1.1, TDI 7.0, or TDI 7.1.

If you are adding features, and the Server feature was already installed, this panel will not be shown.

Server Port Configuration Panel

This panel will only be displayed if new instance of TDI 7.1.1 is getting installed and you have selected the Server to install as a feature or if it is an upgrade installation.

You will be asked for 4 various server ports numbers. There will be default values for these ports. The installer will make sure that you enter a valid and available port number (see Server Port Configuration).

Register Server as a System service panel

This panel will only be displayed if new instance of TDI 7.1.1 is getting installed and you have selected the Server to install as a feature or if it is an upgrade installation. Also this panel will only be displayed if you have Administrative privileges.

If the checkbox is checked, then only SERVER will be registered as a service for that OS.

The default is for the checkbox to be unchecked. The two text boxes will be enabled only if the checkbox is checked. The first text box is for service name and the second is for the port number that the server as a system service will use to run on.

The installer will do its best to provide a valid default value for Service Name (see Registering Server as a Windows service or Unix Process for details on this process). If the installer is unable to determine a valid Service Name, the field will be blank. You will not be able to move forward until you enter a valid service name.

TDI AMC Deployment Panel

This panel is only displayed if the Custom install set was chosen and the you also chose to install the AMC feature. You must choose which ISC instance AMC will be deployed to. You may choose to deploy AMC to the bundled ISC that is shipped with TDI, an ISC that is already installed on the target machine, or choose to deploy AMC at a later time. When choosing an ISC that is already installed, the user must select a directory that contains the embedded Web platform (LWI) or WAS, for example C:\Program Files\IBM\WebSphere\AppServer or C:\dev\IBM\TDI\lwi.

If you did not choose to install the embedded web platform feature, then that choice will be grayed out.

Notes:

1. If you are adding features and the AMC feature is already installed, this panel will be skipped.
2. When deploying AMC to WAS the TDI AMC Admin role is not assigned automatically as when deploying to the embedded Web platform. This role must be manually assigned by the ISC console administrator.

ISC Port panel

This panel is shown either during a typical install or custom install, when you choose to deploy AMC to an Embedded instance of ISC. The ISC instance could be the embedded ISC that is shipped with Tivoli Directory Integrator 7.1.1, or it can be an ISC that is already resident on the target system.

If you are deploying AMC to a custom SE, the default values that are used for the HTTP and HTTPS ports are found as follows:

Look in the TDI_Selected_ISC/conf/overrides/*.properties files for the first occurrence of the properties com.ibm.pvc.webcontainer.port and com.ibm.pvc.webcontainer.port.secure and use the associated values. If either of these properties is not defined in any of the .properties files in that directory, look in TDI_Selected_ISC/conf/config.properties for them. If the HTTP port is not found, it will default to port 80, and if the HTTPS port is not found, it will default to port 443. The help port will have the same value as the HTTP port.

If you are deploying AMC to a custom AE, the default values that are used for the HTTP and HTTPS ports are found as follows (except on i5/OS where the defaults are taken):

Look for files named serverindex.xml file in the following directory specification: TDI_Selected_ISC\profiles\AppSrv01\config\cells\*\nodes\*. Inside those files, look for XML blocks similar to the following for the HTTP port:

<specialEndpoints xmi:id="NamedEndPoint_1200476459036" endPointName="WC_adminhost">
	<endPoint xmi:id="EndPoint_1200476459036" host="*" port="9060"/>
</specialEndpoints>  

and similar to the following for the HTTPS port:

<specialEndpoints xmi:id="NamedEndPoint_1200476459039" endPointName="WC_adminhost_secure">
	<endPoint xmi:id="EndPoint_1200476459039" host="*" port="9043"/> 
</specialEndpoints>

The installer searches for a specialEnpoints tag that has an endPointName of WC_adminhost or WC_adminhost_secure and use the associated port values from the embedded endPoint tags. In the event the HTTP port is not found by this method, it 9060 and in the event the HTTPS port is not found, it will default to 9043. The help port will be set to the HTTP port value.

The values shown are the defaults for the embedded SE.

The panel will not allow ports to be entered that are already in use. A warning message will appear asking you to choose another port value.

Register AMC as a service Panel

If the checkbox is checked, then AMC will be registered as a service for that OS.

The default is for the checkbox to be unchecked.

This panel is only shown if the embedded web platform and AMC features were selected and if you have administrative privileges.

The installer will do its best to provide a valid default value for Service Name (see Registering AMC as a Windows service or Unix process for details on this process). If the installer is unable to determine a valid Service Name, the field will be blank. You cannot move forward until you enter a valid service name.

Pre-Install Summary Panel

This Summary panel gives you a summary of what features will be installed and where they will be installed to.

Installation Progress Panel

This panel is displayed while the actual install is occurring. This panel is the Progress Panel provided by InstallAnywhere. All of the features are installed while this is occurring.

Installation Complete Panel

This panel shows you that the install has completed successfully. When the Done button is pressed, the install is complete. Start the Configuration Editor is checked by default.

Uninstall Panel flow

Uninstall Welcome Panel

This is an InstallAnywhere panel, with standard content.

Choose Product Features Panel

This panel allows you to choose to uninstall the entire product, or only specific features.

If Uninstall Specific Features is chosen, the following panel is also displayed:

Uninstall Progress Panel

This panel is shown during uninstallation.

Uninstall Finish Panel

This panel shows you that the uninstallation has completed successfully. When the Done button is pressed, the uninstaller exits.

Add Feature Panel flow

The Add Feature flow is similar to the new install flow. Only the unique panels will be shown here.

Pre-Initialization Panel

The Welcome Panel

Upgrade Panel

After the Welcome panel and the Previous TDI information panel, if there is an instance of TDI already installed on the box, you will see this panel.

You are not able to choose the Add Feature button if there is no TDI 7.1.1 instance available.

You are not able to choose the Upgrade button if there are no previous versions of TDI available.

The TDI 7.1.1 drop down is enabled if the Add Features button is chosen.

Feature Selection Panel

The next panel in the Add Feature sequence will be the Feature Selection panel, with the already installed features selected and grayed out.

At this point you can add any additional features you choose.

You are not allowed to remove features.

From this point the panel flow matches the new install flow. Panels related to already-installed features will, however, be skipped.

If you select Configuration Editor, Server will also automatically be selected. Also if both features are selected and you deselect Server, then Configuration Editor will also be deselected.

Missing embedded web platform pre-req Panel (i5/OS only)

TDI Solutions Directory Panel

Register Server as a System Service Panel

TDI AMC Deployment Panel

Register AMC as a service Panel

Pre-Install Summary Panel

Installation Progress Panel

Installation Complete Panel

Migration Panel flow

The Migration flow is similar to the new install flow. Only the unique panels will be shown here.

Pre-Initialization Panel

The Welcome Panel

Upgrade Panel

After the Welcome panel and the Previous TDI information panel, if there is an instance of TDI already installed on the box, you will see this panel:

You are not able to choose the Add Feature button if there is no TDI 7.1.1 instance available.

You are not able to choose the Upgrade button if there are no previous versions of TDI available.

The previous TDI version drop down is enabled if the Upgrade button is chosen.

TDI 6.0 Upgrade Flow

If you choose to upgrade a TDI 6.0 instance, the next panel shown will be the License panel and after accepting the license, the Install Type panel. If the customer chooses a Custom install, then the normal Feature list will be presented.

If you choose to install the Server feature, the TDI Solutions Directory panel will be skipped; the value will be obtained from the TDI 6.0 install.

If you choose to install AMC, you will see the normal panels.

If the installer detects that the TDI 6.0 instance used Cloudscape, you will see this panel:

TDI 6.1.x, 7.0 Upgrade Flow

If you choose to upgrade TDI 6.1, 6.1.1 or 7.0, the next panel you will see will be the License panel and after accepting the license, the Feature selection panel:

It will show those features (selected) that were already installed in the previous version, and allow you to add new ones. You are not allowed to disable features that were previously installed.

If the Server was previously installed, the TDI Solutions Directory panel will be skipped. The installer will use the value from the previous installation.

If AMC was previously installed, you will still see the Choose ISC panel, in a TDI 6.x.x migration.

The rest of the panel flow is the same as a new install. In a TDI 7.0 migration, there is one new feature: Register server as system service, this panel is only shown after the feature selection panel.

If you select Configuration Editor, Server will also automatically be selected. Also if both features are selected and you deselect Server, then Configuration Editor will also be deselected.

Installing using the command line

The following command line options are supported by the Tivoli Directory Integrator 7.1.1 installer:

-i

Sets the installer interface mode: silent, console or gui.

install_tdiv711_win_x86.exe -f Response File Name -i silent

install_tdiv711_win_x86.exe -i console

-f

Sets the location of a response file (installer.properties file) for the installer to use.

install_tdiv711_win_x86.exe -f installer.properties

This path can be absolute or relative. (Relative paths are relative to the location of the installer.)

-r

Creates a response file.

install_tdiv711_win_x86.exe -r myinstaller.properties

Note:

The Tivoli Directory Integrator 7.1.1 installer creates the tdi_respfile711.txt response file in the system's temporary files directory, even if -r option is not specified. For example:

• On Windows platform, the response file is created in the C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp directory.
• On non-Windows platform, the response file is created in the /tmp directory.

The TDI_install_dir/examples/install directory contains example response files for various installation and uninstallation scenarios.

-D

Passes custom command-line arguments.

install_tdiv711_win_x86.exe -Dmyvar=myvalue

-l

Uses the specified language code (and optional country code) to set the locale for the InstallAnywhere installer.

install_tdiv711_win_x86.exe -l en

install_tdiv711_win_x86.exe -l pt_BR

The required language code is a two-character (commonly lowercase) code defined by the ISO-639 standard. InstallAnywhere accepts both old (iw, ji, and in) and new (he, yi, and id) language codes.

The optional country code is a two-character (commonly uppercase) code defined by the ISO-3166 standard.

Locale options are only respected if the installer includes localizations for the locale you specify.

-?

Shows help for the InstallAnywhere installer.

On Windows, -help only works from the console launcher. Make sure to set the LaunchAnywhere to Console on the Windows tab of the Project > Platforms subtask. (For an installed LaunchAnywhere to provide this information, you need to make sure it is explicitly set to Console Launcher on the action.)

The following command line option is unique to the Tivoli Directory Integrator installation Wizard:

LAX_VM

The LAX_VM parameter is used to boot the installer from Java virtual machine, which is installed on the system.

You need to specify absolute path of the Java executable file that resides in the Java bin directory. For example,

install_tdiv711_win_x86.exe LAX_VM "Java_DIR/jre/bin/java.exe"

Use only the space characters between the arguments.

Note:

Make sure that you use the absolute path of IBM JRE version 1.5 and above, as parameter value. The Tivoli Directory Integrator 7.1.1 installer may not work correctly with other JREs.

-D$TDI_BACKUP$="true"

This parameter should only be passed in on an uninstallation. This parameter is provided for future migration considerations; for example:

TDI_install_dir\_uninst\uninstaller.exe -D$TDI_BACKUP$="true"

This instructs the uninstaller to run the TDI_install_dir/bin/tdiBackup.bat(.sh) script, which in turn will cause a directory TDI_install_dir/backup_tdi to be created. A backup of a number of files particular to your installation will be stored into this directory, including your global properties files, global certificates and the like.

-D$TDI_SKIP_VERSION_CHECK$="true"

This parameter will cause the installer to skip any previous version checks. This essentially disables any migration from previous releases.

In a silent install, if this skip option is chosen and the install directory is same as an earlier installation of Tivoli Directory Integrator V7.1.1, it will cause the installer to stop.

-D$TDI_NOSHORTCUTS$="true"

This parameter is used to stop the installer from creating any shortcuts to the uninstaller, CE, or AMC.

Temporary file space usage during installation

During installation, the installer may use a substantial amount of temporary file space in order to stage files. If your system is constrained in this regard, errors during installation might occur.

UNIX/Linux systems typically use /tmp or /var/tmp as temporary files storage, whereas on Windows, the temporary file storage area is found in the location pointed to by the environment variable TEMP.

InstallAnywhere installers can be instructed to redirect their temporary file usage by setting the environment variable IATEMPDIR before starting the installer. For example, on UNIX:

export IATEMPDIR=/opt/IBM/TDI/temp

Then, start your console mode installers from the session in which you have set the IATEMPDIR variable.

Performing a silent install

To perform a silent installation you must first generate a response file. To generate this file, perform a non-silent installation with the -r option specified, for example:

install_tdiv711_win_x86.exe -r Response File Name

The response file is created in the directory that you specify during installation.

Once the response file is created, you can install silently using the following command:

install_tdiv711_win_x86.exe -i silent -f Response File Name

Post-installation steps

CE Update Site

If the CE Update site was installed, you now have to manually deploy into Eclipse. See the section entitled Installing or Updating using the Eclipse Update Manager for more information.

Plug-ins

If any of the password synchronization plug-ins were installed, see the IBM Tivoli Directory Integrator V7.1.1 Password Synchronization Plug-ins Guide for information on how to deploy the plug-in code.

Administration and Monitoring Console (AMC)

General information

• For more information on AMC, see Administration and Monitoring.
• When you are ready to log into the console, browse to http://hostname:port/ibm/console. For more information, see section Log in and logout of the console.
• For more information on adding users and user roles, see section Console user authority.

Bundled embedded web platform deployment

• If you installed AMC with the bundled embedded web platform and are ready to use AMC, you will need to run the commands to start AMC and Action Manager (AM) before you can log into the ISC console. For more information, see section Starting the Administration and Monitoring Console and Action Manager and logging in.
  Note:

  On Windows, a shortcut to the launchAMC.html file is created in the start menu under Program Files.
• By default, the user who installs Tivoli Directory Integrator is the only one with access to log in to the console.

Customer or deferred deployment

• If you chose a custom Tivoli Integrated Portal (ISC embedded) to deploy AMC to, and are now ready to deploy, see Deploying AMC to a custom ISC SE or Tivoli Integrated Portal (ISC embedded). When deploying AMC in such a way the installer does not automatically assign the current user the TDI AMC Admin role. This right needs to be manually authorized by an administrator of the ISC console. This is typically done using the Users and Groups -> Administrative User Roles panel of the Tivoli Integrated Portal (ISC embedded) console. Alternatively this role could be assigned using the setAMCRoles command.
• If you chose to defer deployment of AMC into an ISC and are ready to do so, see section Deploying AMC to a custom ISC SE or Tivoli Integrated Portal (ISC embedded).
  Note:

  If you have done a custom ISC SE/AE deployment then at a minimum you will need to ensure that AM is started after you start the ISC SE/AE that AMC was installed into.

Documentation

The documentation system used by Tivoli Directory Integrator is the IBM Eclipse Help System. After you have done a default installation, this means that IBM Tivoli Directory Integrator 7.1.1 documentation is made available to you online, on the Web in the form of an Infocenter hosted by IBM. You may, however, choose to deploy the documentation locally. For more information, see Installing local Help files.

If you are new to Tivoli Directory Integrator, we recommend that you read and step through the IBM Tivoli Directory Integrator V7.1.1 Getting Started in order to get used to the concepts used.

If you have used earlier versions of Tivoli Directory Integrator, then chapter 3 of the IBM Tivoli Directory Integrator V7.1.1 Users Guide will be very beneficial to you in order to understand the new IDE framework and layout. It will also explain how you can import and open your existing configurations; and how the Server still uses the Config model at runtime.

Migration

If you have used an earlier version of Tivoli Directory Integrator, then you will most likely need to migrate certain aspects of your previous deployment. More information on what to do in this case can be found under Migrating.