Solaris 10 5/09 Release Notes

iPlanet Directory Server 5.1 Issues

This section provides important information for users of iPlanetTM Directory Server 5.1 who are upgrading to the new Solaris 10 release.

Installing Directory Server 5.1

Sun Java System Directory Server 5 2005Q1 replaces iPlanet Directory Server 5.1 that was integrated in the Solaris 9 Operating System. In Solaris 10 OS, this new Directory Server can be installed as part of the Sun Java Enterprise System.


Note –

For information about the Sun Java System Directory Server 5 2005Q1, refer to the documentation for the Sun Java System at http://docs.sun.com.


Solaris 10 OS continues to support Directory Server 5.1. You might need to install Directory Server 5.1 under the following circumstances:

In Solaris 10 release, you install the Directory Server 5.1 manually. Follow these steps:

  1. Insert the Solaris 10 Software - 5 CD into your CD-ROM drive.

  2. Become superuser.

  3. In a terminal window, install the Directory Server.


    # cd /cdrom/cdrom0/Solaris_10/Product/
    # pkgadd -d . IPLTnls IPLTnspr IPLTnss IPLTjss IPLTpldap \
    IPLTdsr IPLTdsu IPLTadmin IPLTcons IPLTadcon IPLTdscon \
    IPLTadman IPLTdsman
    

    To install Simplified Chinese localization packages, issue the following additional command:


    # pkgadd -d . IPLTcdsu IPLTcadmin IPLTccons IPLTcadcon \
    IPLTcdscon IPLTcadman IPLTcdsman
    

    To install Japanese localization packages, issue the following additional command:


    # pkgadd -d . IPLTjdsu IPLTjadmin IPLTjcons IPLTjadcon \ 
    IPLTjdscon IPLTjadman IPLTjdsman
    
  4. After installation is complete, configure iPlanet Directory Server 5.1. Refer to Chapter 11, Sun ONE Directory Server Configuration, in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) .

Migrating to the Sun Java System Directory Server 5 2005Q1


Caution – Caution –

The database formats of the two Directory Server versions are incompatible. Thus, if you are a Directory Server 5.1 user, Sun recommends that you migrate your database to a database that is formatted for the Sun Java System Directory Server 5 2005Q1.


To perform a migration, both versions of the Directory Server must exist in the system that has been upgraded to the Solaris 10 OS. If you are a DS 5.1 user, but are using the compressed archive (.tar.gz) delivery format, you can skip immediately to the migration instructions in Step 2.

  1. On a terminal window, check whether iPlanet Directory Server 5.1 packages are present in your system.


    $ pkginfo | grep IPLT
    

    If the following packages appear as output, then you can go to Step 2 to proceed with the migration. The output indicates that the iPlanet Directory Server 5.1 packages are in the system.


    system  IPLTadcon  Administration Server Console
    system  IPLTadman  Administration Server Documentation
    system  IPLTadmin  Administration Server
    system  IPLTcons   Console Client Base
    system  IPLTdscon  Directory Server Console
    system  IPLTdsman  Directory Server Documentation
    system  IPLTdsr    Directory Server (root)
    system  IPLTdsu    Directory Server (usr)
    system  IPLTjss    Network Security Services for Java
    system  IPLTnls    Nationalization Languages and Localization Support
    system  IPLTnspr   Portable Runtime Interface
    system  IPLTnss    Network Security Services
    system  IPLTpldap  PerLDAP
    $

    If the packages do not exist, then install the iPlanet Directory Server 5.1 packages first. Refer to the 4-step procedure in the preceding section Installing Directory Server 5.1. After installation is complete, go to Step 2 to proceed with the migration.

  2. Migrate your iPlanet Directory Server 5.1 database to the current version. For instructions, refer to the documentation collection for the Sun Java System Directory Server at http://docs.sun.com/coll/DirectoryServer_05q1.

After migrating your data, make sure you continue to back up directory data in the same way as you backed up directory data before migration. Future disaster recovery might require the migrated database.