Home > Articles > Operating Systems, Server > Solaris

  • Print
  • + Share This
Like this article? We recommend

Sun ONE Directory Server 5.2 Configuration

Before you configure the Directory Server or Administration Server, you need to make sure the appropriate packages are installed and proper patches are applied. Check the Installation and Tuning Guide for more information. You do not need to remove the iPlanet Directory Server 5.1 software, but you should make sure no Directory Server or Administration Server instances are running. Otherwise, you would not be able to use the port numbers they are running on.

When the new packages are installed, be aware of the following:

  • The existing /usr/sbin/directoryserver wrapper script is renamed /usr/sbin/directoryserver.51bak.

  • The /usr/sbin/directoryserver wrapper script is replaced with a link to an updated one located at /usr/ds/v5.2/sbin/directoryserver.

  • The /etc/init.d/directory startup script is overwritten.

  • A new wrapper script called /usr/sbin/mpsadmserver, that is used to manage the Administration Server, is installed.

  • The SUNWzlib and SUNWzlibx packages must be loaded in order to un-compress the Directory Server packages.

  • The SUNWj3rt package must contain Java Runtime Environment 4.1 and a version of 4.1.1 or higher is highly recommended.

  • There is a new script to start the Console: /usr/sbin/mpsconsole

Performing the Configuration

The /usr/sbin/directoryserver wrapper script is used to perform configuration on the Directory Server. Some noticeable differences from the prior version are:

  • The configure option is specified instead of setup.

  • The configuration program uses a graphical interface unless the -nodisplay option is specified.

  • The Administration Server configuration is not performed.

To configure the Directory Server without the graphical display, run the following:

# /usr/sbin/directoryserver configure -nodisplay

During the configuration, you are prompted for the server root or installation directory. This is where the Directory Server instance files you created will be placed along with Administration Server configuration data. The default is /var/mps/serverroot. You should not specify a symbolic link because this affects the ability to start the Administration Server as any user other than root.

To configure the Administration Server, run the following command:

# /usr/sbin/mpsadmserver configure -nodisplay

Silent Installations

To run the Directory Server installation in silent mode, edit the following template file and specify it as input to the directoryserver(1M) command. An example of the template, with comments removed is shown below.

# cat /usr/ds/v5.2/setup/typical.ins
[STATE_BEGIN Sun ONE Directory Distribution 
727642c18dde6631814c2884e6eb5e676eb89bb0]

ProductServerRoot = ProductServerRootPathValue

FullMachineName = FullMachineNameValue

ServerUser = UserID
ServerGroup = GroupID

UseExistingConfigDirectory = 0

UseExistingUserDirectory = 0

DirectoryIdentifier = InstanceName
DirectoryPort = LDAPPort
DirectorySuffix = BaseSuffix

ConfigDirectoryAdminID = AdminUserID
ConfigDirectoryAdminPwd = AdminUserPasswd

AdminDomain = AdministrationDomain

DirectoryManager = DirectoryManagerDN
DirectoryManagerPwd = DirectoryManagerPasswd

[STATE_DONE Sun ONE Directory Distribution 
727642c18dde6631814c2884e6eb5e676eb89bb0]
#

After renaming the template file, run the following command to perform the silent installation.

# /usr/sbin/directoryserver configure 
-nodisplay -noconsole -state mydirconfig.ins

The Administration Server can be configured silently in a similar manner by editing a template file and specifying it as input to mpsadmserver(1M).

# cat /usr/sadm/mps/admin/v5.2/setup/admin/typicalInstall.ins
[STATE_BEGIN Sun ONE Administration Distribution 
470bfd35d167a2a0ddde6c29a2ea8d4fb4e39fe6]

ProductServerRoot = ProductServerRootPathValue

FullMachineName = FullMachineNameValue

ServerUser = UserID
ServerGroup = GroupID

ConfigDirectoryHost = ConfigDirectoryHostValue
ConfigDirectoryPort = ConfigDirectoryPortValue

ConfigDirectoryAdminID = ConfigDirectoryAdminIDValue
ConfigDirectoryAdminPwd = ConfigDirectoryAdminPwdValue

AdminDomain = AdminDomainValue

AdminPort = AdminPortValue


[STATE_DONE Sun ONE Administration Distribution 
470bfd35d167a2a0ddde6c29a2ea8d4fb4e39fe6]
#

# /usr/sbin/mpsadmserver configure -nodisplay -noconsole -state 
myadminconfig.ins

Changes to RFC 2307 Schema Files

Several changes have been made to the 11rfc2307.ldif file in the Sun ONE Directory Server 5.2 schema directory. Some of these changes might affect you if you have an existing deployment of the Secured LDAP Client. Issues include:

  • Removal of the automount object class and the automountInformation attribute.

  • These are added to the 99user.ldif schema file when the idsconfig(1M) command is run to configure the Directory Server to support Secured LDAP Clients. This should have no effect because those definitions would have to be manually removed for the 11rfc2307.ldif file anyway before running idsconfig(1M).

  • The ipHost object class no longer allows the o, ou, owner, seeAlso, and serialNumber attributes.

  • If you used the ldapaddent(1M) command to populate the directory, there will be no issue. If you defined your own ipHost entries that specify those attributes, you must use the old schema or modify the entries.

  • The ieee802Device object class no longer includes cn as a mandatory attribute nor allows the l, o, ou, owner, seeAlso and serialNumber attributes.

  • This will have an impact if ldapaddent(1M) is used to create entries for the ethers database because cn is defined as an attribute.

  • The bootableDevice object class no longer includes cn as a mandatory attribute nor allows the l, o, ou, owner, seeAlso and serialNumber attributes.

  • This will have an impact if ldapaddent(1M) is used to create entries for the bootparams database because cn is defined as an attribute.

  • + Share This
  • 🔖 Save To Your Account