On SuSE Linux:
Directory Server Enterprise Edition for SuSE Linux is available only in the zip distribution. Identity Synchronization for Windows and Directory Editor components are not supported.
On SuSE Linux 9, you must have SP4 on your system. If SP4 is not installed on your SuSE Linux 9 computer, upgrade your operating system. You can install Directory Server Enterprise Edition using any of the following procedures:
Install Directory Server Enterprise Edition 6.3 zip distribution directly on SuSE Linux 9 SP4 system as mentioned in this section.
Upgrade the previous Directory Server Enterprise Edition 6.2 zip installation. As Directory Server Enterprise Edition 6.2 supports only SuSE Linux SP3, you must upgrade your operating system to SuSE Linux SP4 before upgrading Directory Server Enterprise Edition to 6.3. For more details, refer to the To Upgrade Directory Server Enterprise Edition From Zip Distribution section.
On SuSE 64-bit, .pam-32bit-9-yyyymmddhhmm.rpm is a prerequisite for cacao to start. You must install it if not already present on your system.
SuSE Linux Enterprise Server provides a set of scripts in /etc/profile.d/ to automatically set the appropriate environment as per the installed software. Therefore, you must reset the following Java environment variables to none before you start working on the product using commands.
JAVA_BINDIR
JAVA_HOME
JRE_HOME
JAVA_ROOT
On HP-UX:
You must have HP-UX 11.23 installed on your computer. If not, you must upgrade your operating system. You can install Directory Server Enterprise Edition using any of the following procedures:
Install Directory Server Enterprise Edition 6.3 zip distribution directly on HP-UX 11.23 system as mentioned in this section.
Upgrade the previous Directory Server Enterprise Edition 6.0 or 6.1 zip installation. As Directory Server Enterprise Edition 6.0 and 6.1 support only HP-UX 11.11, you must upgrade your operating system to HP-UX 11.23 before upgrading Directory Server Enterprise Edition to 6.3. For more details, refer to the To Upgrade Directory Server Enterprise Edition From Zip Distribution section.
Patch Table for Zip Distribution
Refer to the following table for information about the appropriate zip patch for your system. If newer patch revisions become available, use the newer ones instead of those shown in the table.
Operating System |
Patch number |
---|---|
Solaris SPARC | |
Solaris 9 x86 | |
Solaris 10 x86 and AMD x64 | |
Red Hat Linux | |
SuSE Linux | |
HP-UX | |
Windows |
All the multilingual files are included in the above mentioned patches.
Complete the worksheet given below before you start your installation.
By default, the user and group IDs for zip installations are those of the user performing the installation.
Obtain the zip distribution for this installation.
Install the prerequisite patches or service packs for your platform.
Change to the zip distribution directory that contains the dsee_deploy command.
Install the software with the dsee_deploy(1M) command.
$ ./dsee_deploy install -i install-path options |
On Windows, browse to the zip distribution folder that contains the dsee_deploy command and run the following command:
dsee_deploy install -i install-path options |
For example, the following command installs the component in the /local directory, assuming that you have write access to the directory.
$ ./dsee_deploy install -i /local |
You can also use the --no-inter option to install in non-interactive mode, accepting the license without confirmation. Non-interactive mode is particularly useful for silent installation.
This step installs a Common Agent Container, cacao, with the local Directory Service Control Center agent as well, allowing you to use DSCC to create server instances. The previous command works properly only if you have not yet installed a Common Agent Container using the default port, 11162.
If you installed DSCC previously on the same system, a Common Agent Container using the default port is already installed. Specify a different port using the -p option.
$ ./dsee_deploy install -i /local -p 11169 |
During the installation process, a WAR file is saved on your system. The WAR file contains the DSCC web application which when deployed with the application server enables you to access and manage the server instances through web console. The functionality is similar to DSCC in native packages. For more information about WAR file, see Installing Directory Service Control Center From Zip Distribution.
During the installation process, the multilingual packages are also installed.
(Optional) Load sample data in your directory.
Examples that use command-line tools depend on sample data residing under the dc=example,dc=com suffix of your directory.
You can set up part of the data that is required by creating a dc=example,dc=com suffix. You can then populate the suffix with entries from the ds6/ldif/Example.ldif file.
Create a new Directory Server instance and start the instance.
$ dsadm create -p port -P SSL-port instance-path $ dsadm start instance-path |
Read the Example.ldif file to find bind passwords needed in the examples.
Create suffix and load the Example.ldif content into the directory by using the following commands:
$ dsconf create-suffix -h localhost -p 1389 dc=example,dc=com $ dsconf import -h localhost -p 1389 install-path/ds6/ldif/Example.ldif \ dc=example,dc=com |
For more information, see To Create a Directory Server Instance From the Command Line.
Generate test data for examples by using the makeldif(1) command and the following template:
define suffix=dc=example,dc=com define maildomain=example.com branch: ou=test,[suffix] subordinateTemplate: person:100 template: person rdnAttr: uid objectclass: top objectclass: person objectclass: organizationalPerson objectclass: inetOrgPerson givenName: <first> sn: <last> cn: {givenName} {sn} initials: {givenName:1}{sn:1} employeeNumber: <sequential> uid: test{employeeNumber} mail: {uid}@[maildomain] userPassword: auth{employeeNumber}{employeeNumber} telephoneNumber: <random> description: This is the description for {cn}.
Copy the template content to template.ldif and use commands such as the following to generate the data in test.ldif and to load the content into the directory.
$ cd install-path/dsrk6/bin/example_files/ $ ../makeldif -t test.template -o test.ldif Processing complete. 101 total entries written. $ ../ldapmodify -a -c -D uid=hmiller,dc=example,dc=com -w - -f test.ldif Enter bind password: … |
If you read Example.ldif, you see that the password for hmiller is hillock.
After installing the software, see Environment Variables.