Siebel Security Guide > Security Adapter Authentication > Process of Installing and Configuring LDAP Client Software >

Installing the IBM LDAP Client and IBM GSKit on Oracle Solaris


This topic describes how to install the IBM LDAP Client and IBM GSKit on Oracle Solaris. Before installing the IBM LDAP Client and GSKit, you must relocate any non-IBM LDAP files that exist on Oracle Solaris; this task is also described in this topic.

This task is a step in Process of Installing and Configuring LDAP Client Software.

Relocating Non-IBM LDAP Files on Your System

LDAP files are included in most Oracle Solaris installations and, if they exist, they must be moved from the /usr/bin/ directory before the IBM LDAP Client files can be installed. You can relocate the Oracle Solaris LDAP files either before or during the IBM Client and GSKit installation. Each method is described in this topic.

To relocate the Oracle Solaris LDAP files before you begin to install the IBM LDAP files, use the following procedure.

To relocate the Oracle Solaris LDAP files on your system

  1. Locate the Oracle Solaris LDAP files by entering the following command:

    ls -al |grep ldap

  2. Move the files you locate from /usr/bin to a directory of your choice, for example, /usr/bin/ldapsparc.
  3. Proceed to install the IBM LDAP Client and GSKit.

If you do not relocate the Oracle Solaris LDAP files before you begin to install the LDAP Client and GSKit, you can relocate them during the LDAP Client installation, as described in the following procedure.

To relocate the Oracle Solaris LDAP files during the IBM LDAP Client and GSKit installation

  1. If non-IBM LDAP files are detected during the IBM LDAP Client installation, the following message is displayed:

    A non-IBM version of LDAP has been located on your system.
    In order to use the command-line version of the IBM-supplied files, the existing files (ldapadd, ldapdelete, ldaplist, ldapmodify, ldapmodrdn, ldapsearch) must be relocated.

    (/usr/bin/ldapsparc) [?,q]

    Specify the name of the directory where you want to move the non-IBM LDAP files by doing one of the following:

    • Press Enter to accept the default directory, /usr/bin/ldapsparc
    • Type a different directory path name, and press Enter

      Alternatively, type q and press Enter to quit.

  2. After relocating the files, a number of messages are displayed and then the following prompt appears:

    Do you want to install these conflicting files [y,n,?,q]

    Type y and press Enter to continue the installation of the IBM LDAP files.

    The existing Oracle Solaris LDAP files are moved to the directory you specified in Step 1 and the IBM LDAP Client files are installed in the /usr/bin directory.

Installing the IBM LDAP Client and GSKit Installation Files on Oracle Solaris

The following procedure describes how to install the IBM LDAP Client and GSKit.

To obtain IBM LDAP Client and IBM GSKit installation files on Oracle Solaris

  1. Login as root.
  2. Navigate within the Siebel network image to the directory Solaris/Server_Ancillary/IBM_LDAP_6.0_Client/enu.

    This directory contains two files:

    • itds60-client-sol-sparc-ismp.tar

      Choose this file if you want to use an installation wizard to install the IBM LDAP Client and IBM GSKit.

    • itds60-client-sol-sparc-native.tar

      Choose this file if you want to install the IBM LDAP Client and IBM GSKit using the command line.

  3. Copy one of the files described in Step 2 to an empty directory that has at least 50 MB of available space.
  4. Enter the following command:

    tar -xvf nameOfSelectedFile.tar

    The directory nameOfSelectedFile is created at the current location and the IBM LDAP Client and IBM GSKit files are unpacked and installed into it.

  5. Add the directory path of the IBM LDAP 6.0 libraries to the library path environment variable in either the siebenv.csh (C shell) or siebenv.sh (Bourne or Korn shell) script file. For information on this task, see Configuring the siebenv.csh and siebenv.sh Scripts for the LDAP Client.
  6. Stop and restart the Siebel Server.
Siebel Security Guide Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.