Introduction to IBM Tivoli Directory Server 6.0 – Installation and Configuration Using InstallShield MultiPlatform (ISMP) Excerpt taken from presentation given on April 10, 2007Creating an IBM Tivoli Directory Server instance after an ISMP Installation Introduction to IBM Tivoli Directory Server 6.0 – Installation and Configuration Using InstallShield MultiPlatform (ISMP) Excerpt taken from presentation given on April 10, 2007 Creating an IBM Tivoli Directory Server instance after an ISMP Installation ISMP Installation Complete ISMP Installation Complete After you install a server, you must perform the following configuration tasks before you can use the server: Create user IDs for the directory server instance owner and, for some installations, the database instance owner and the database owner. See Appendix D. Setting up users and groups: directory server instance owner, database instance owner, and database owner for detailed information about these user IDs. Create a directory server instance. Set the IBM Tivoli Directory Server administrator distinguished name (DN) and password for the directory server instance. Create and configure the database. The IBM Tivoli Directory Server Instance Administration Tool is automatically launched after the ISMP installation has completed. Creating Users and Groups Creating Users and Groups Create a Db2 Administrator group named “db2admin” Create a new user, whose primary group is the “db2admin” group and make them a member of the idsldap group. Set the password for the new user. su - Again su - and enter the password You will be prompted to enter a new password Enter the new password for this user and confirm the password Idsxinst – create a new directory server Instance Idsxinst – create a new directory server Instance The IBM Tivoli Directory Server Instance Administration Tool is automatically launched after the ismp install has completed. You will use this tool to create your IBM Tivoli Directory Server Instance. Click the “Create” button to begin. Idsxinst – create a new directory server Instance Idsxinst – create a new directory server Instance The “Create new directory server instance” window will appear. Select “Create a new directory server instance” and click “Next”. Idsxinst – create a new directory server Instance Idsxinst – create a new directory server Instance Enter the User name you created in slide 22. Enter the Install location for this instance. Enter the Encryption seed string for this instance. (**Make note of this value) Optionally you may enter a description for this instance. Idsxinst – create a new directory server Instance Idsxinst – create a new directory server Instance Select the DB2 instance name and click “Next”. Idsxinst – create a new directory server Instance Idsxinst – create a new directory server Instance By default the “Listen on all configured IP addresses” will be selected, click the “Next” button to continue configuring the new directory server instance. Idsxinst – create a new directory server Instance Idsxinst – create a new directory server Instance Each directory server instance is associated with four unique ports. The default settings are shown above. Click the “Next” button to continue with the default TCP/IP port settings. Idsxinst – optional steps Idsxinst – optional steps Select “Configure admin DN and password” and “Configure database” and click the “Next” button. Idsxinst – create and configure the database Idsxinst – create and configure the database Enter the Database user name Enter the password for the Database user name Enter the Database name and click “Next”. Idsxinst – create and configure the database Idsxinst – create and configure the database To create a UTF-8 database in the directory server instance location, click “Next” to continue. Idsxinst – confirm selections Idsxinst – confirm selections Confirm your configuration selections and click “Finish” to Create the new directory server instance Create the new database instance Set the Administrator DN and password Create and configure the new database. Idsxinst – task completed Idsxinst – task completed When the creation and configuration is complete, you will see a pop up window indicating that the task is complete. Click “OK” to close the window. Note in the main idsxinst window there is now an entry for the new directory instance just created. Idsxinst – exit the results panel Idsxinst – exit the results panel Click “Close” to close the results panel. Idsxinst – exit the idsxinst utility Idsxinst – exit the idsxinst utility Click “Close” to exit the idsxinst utility. Idsxinst – confirm and exit the idsxinst utility Idsxinst – confirm and exit the idsxinst utility After click the “Close” button on the previous slide, a pop up window will ask you to confirm whether or not you really want to exit the tool. Click “Yes” to exit the idsxinst tool. idsxcfg - configure a suffix idsxcfg - configure a suffix Launch the “idsxcfg” utility by issuing “idsxcfg from the command prompt. **Note: You can also configure a database and set the Administrator DN and password from this utility as well Idsxcfg - configure a new Suffix DN Idsxcfg - configure a new Suffix DN Select “Manage suffixes” from the left hand navigation panel. This will load the “Manage suffixes” panel. Idsxcfg - configure a new Suffix DN Idsxcfg - configure a new Suffix DN Enter the new Suffix DN and click “Add”. Idsxcfg – commit the Suffix DN changes Idsxcfg – commit the Suffix DN changes Click the “OK” button to commit the changes. Idsxcfg – suffix configuration complete Idsxcfg – suffix configuration complete Once you have committed the changes to the “Manage suffixes” panel, the Overview panel is displayed. You are now ready to proceed to load data into the directory server database. Idsxcfg – load the sample data Idsxcfg – load the sample data Select “Import LDIF data” from the left navigation panel. Idsxcfg – load the sample data Idsxcfg – load the sample data Click the browse button to select the location of the ldif file that you wish to import. In the “/opt/IBM/ldap/V6.0/examples” directory a sample ldif file named “sample.ldif” is provided with the installation. The sample ldif file contains a static group definition, multiple subtree definitions and 50 user entries. Structural Layout of sample.ldif Structural Layout of sample.ldif dn: o=IBM, c=US objectclass: top objectclass: organization o: IBM dn: ou=Austin, o=IBM, c=US ou: Austin objectclass: top objectclass: organizationalUnit seealso: cn=Linda Carlesberg, ou=Austin, o=IBM, c=US dn: ou=Groups, o=IBM, c=US objectclass: top objectclass: organizationalUnit ou: Groups Users Users Users Members The top level entries for the sample.ldif file are defined as follows. These entries must be loaded before any user data can be loaded. The sample.ldif file contains these entries in the beginning of the ldif so the user entries can be loaded as part of the same file. dn: o=IBM, c=US objectclass: top objectclass: organization o: IBM dn: ou=Austin, o=IBM, c=US ou: Austin objectclass: top objectclass: organizationalUnit seealso: cn=Linda Carlesberg, ou=Austin, o=IBM, c=US dn: ou=In Flight Systems, ou=Austin, o=IBM, c=US ou: In Flight Systems objectclass: top objectclass: organizationalUnit description: main product:Course Maker businessCategory: aircraft seealso: cn=Maria Garcia, ou=In Flight Systems, ou=Austin, o=IBM, c=US dn: ou=Home Entertainment, ou=Austin, o=IBM, c=US ou: Home Entertainment objectclass: top objectclass: organizationalUnit description: Home Entertainment product development businessCategory: Home Entertainment dn: ou=Groups, o=IBM, c=US objectclass: top objectclass: organizationalUnit ou: Groups dn: cn=Bowling team, ou=Groups, o=IBM, c=US objectclass: top objectclass: groupOfNames description: IBM Austin Bowling Team cn: Bowling team owner: cn=Mary Burnnet, ou=Widget Division, ou=Austin, o=IBM, c=US member: cn=Mary Burnnet, ou=Widget Division, ou=Austin, o=IBM, c=US member: cn=Michael Campbell+postalcode=4609, ou=Widget Division, ou=Austin, o=IBM,c=US member: cn=Eddie Catu, ou=In Flight Systems, ou=Austin, o=IBM, c=US member: cn=Melinda Charles, ou=In Flight Systems, ou=Austin, o=IBM, c=US member: cn=Al Edwards, ou=Widget Division, ou=Austin, o=IBM, c=US dn: ou=Widget Division, ou=Austin, o=IBM, c=US ou: Widget Division objectclass: top objectclass: organizationalUnit description: main product:Orange Widget Delux businessCategory: home entertainment Idsxcfg – load the sample data Idsxcfg – load the sample data Scroll to the bottom of the panel and click the “Import” button to begin loading the sample ldif file. Idsxcfg – load the sample data is now complete Idsxcfg – load the sample data is now complete Once the ldif file is loaded, a success message indicating the number of entries loaded is displayed in the “Task messages” panel. Click the “Close” button to exit the “Import LDIF data” panel. Copyright and trademark information Copyright and trademark information © Copyright IBM Corporation 2000 - 2007. All rights reserved. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM web site pages may contain other proprietary notices and copyright information which should be observed. IBM trademarks http://www.ibm.com/legal/copytrade.shtml#ibm Fair use guidelines for use and reference of IBM trademarks http://www.ibm.com/legal/copytrade.shtml#fairuse General rules for proper reference to IBM product names http://www.ibm.com/legal/copytrade.shtml#general Special attributions IBM, the IBM logo and DB2 are trademarks of International Business Machines Corporation in the United States, other countries, or both. MMX, Pentium, and ProShare are trademarks of Intel Corporation in the United States, other countries, or both. Microsoft and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product or service names may be trademarks or service marks of others.