![]() |
iPlanet Delegated Administrator 4.5 Deployment and Customization Guide |
Appendix B Upgrading from Delegated Administrator Version 4.11
This appendix describes modifcations you must make to your directory information tree (DIT) in order to upgrade an existing Netscape Delegated Administrator 4.11 installation to iPlanet Delegated Administrator 4.5. The appendix contains the following topics:
Changes from Version 4.11 to Version 4.5
Add New Objectclasses and Attributes
Importing New Configuration Information
Initializing the Object Counters
Changes from Version 4.11 to Version 4.5
In order to support user directories that are already deployed, Delegated Administrator 4.5 uses a new, highly flexible DIT model. It defines a new grammar that is capable of creating an abstract representation of the user tree which can be interpretted by the back end. By making a few changes in your existing user directory, and representing your existing tree in terms of the new grammar, you can use Delegated Administrator 4.5 to with the user directory you created using version 4.11.Figure B-1 illustrates the default DIT used in Delegated Administrator 4.11.
Figure B-1    Default DIT used in Delegated Adminstrator 4.11 ![]()
Changes and additions were necessary to introduce flexibitlity in the support of arbitrary DITs. Figure B-2 illustrates the resulting default DIT used in Delegated Administrator 4.5.
Figure B-2    Default DIT in Delegated Administrator 4.5 ![]()
Modifying the User Directory
Before Delegated Administrator 4.5 can work with the administrators created using Delegated Administrtor 4.11, you must modify entries at the Top level and at the Organization level of your existing tree.
Step 1: Modify Entries at the Top Level
Rename the top level cn=Help Desk administrators group to cn=Service Help Desk Administrators.
Create ou=Groups, <base suffix>
Move the Service Help Desk and Service Administrator Groups to under ou=Groups, <base suffix>.
Add the cn=domainConfiguration tree under ou=config, <base suffix>.
Step 2: Modify Entries at the Organization Level
Rename cn=Dept Administrators, <domain dn> to cn=Domain Department Administrators, <domain dn>.
Rename cn=Help Desk administrators to cn=Domain Help Desk Administrators.
Move the cn=Domain Administrators group, cn=Domain Help DeskAdministrators group and the cn=Domain Department Administrator group to under ou=Depts, <domain dn>
Add New Objectclasses and Attributes
New ACIs, objectclasses, and attributes were added in Delegated Administrator 4.5. Before you install version 4.5, you must modify the following entries created by Delegated Administator 4.11:
Step 1: Modify the Top-level Entry
nsDefaultMaxDeptSize
Step 2: Modify Each Organization Entry
Add the new Domain Level ACI replacing the old. If you had made ACI changes to the original NDA4.11 ACI at the domain level, you may need to make corresponding changes in the new set for iDA4.5. The following acis need to be added at the domain level :
Step 3: Modify the NDAUser Entry
Set the NDAUser userpassword to auth (default password set in the servlet/resource.properties file). You may want to change this password in both places after installing iDA against the user DIT.
Step 4: Modify Administrator Group Entries
All administrator groups should be modified as follows
Add objectclass: nsManagedDeptAdminGroup to the entry.
Add objectclass: inetAdmin to the entry.
Remove objectclass: nsManagedDept from the entry, if it exists.
Add adminRole: <rdn of the Administrative Group entry> e.g.
To the Service Administrators group add the attribute -> adminRole: Service Administrators
Remove nsNumUsers and nsMaxUsers from the Administrator group entry if they exist.
For the Department level Administrator groups, rename the group rdn from cn=Dept Administrators to cn=Department Administrators. Make corresponding changes from Dept to Department in all places where this dn exists as an attribute value.
Step 5: Modify OrgUnit Entries
Add objectclass: nsManagedOrgUnit to the ou=Users & ou=Depts entries.
Step 6: Modify Department or Group Entries
Add attributes nsNumDepts & nsMaxDepts with appropriate values to each entry.
Change the attribute name 'owner' to 'nsDAModifiableBy' and retain the old attribute value.
Step 7: Modify User Entries
Since UID translation is no longer supported in iDA4.5, the uid value in each entry needs to be changed to just the userID without the domain name suffixed to it. Corresponding changes would need to be made in the user tree if UID translation was on. For example:uid=bill-Airius.com will now become uid=bill.
All references to the user entry would need to be modified accordingly.
Change the attribute name 'nssearchfilter' to 'nsDADomain' and retain the old attribute value.
Change the attribute name 'ou' to 'memberOf' and retain the old attribute value.
Importing New Configuration Information
Delegated Administrator 4.5 configuration information, which formerly existed on the file system, has been moved into the directory server. This allows other applications to access the configuration and leverage the DIT structure information. This arrangement also allows other applications to garner additional useful information on predefined search datatypes and other generic parameters from the configuration. Since this information was absent in the NDA4.11 DIT, it needs to be imported into the user tree.
To Import Configuration Changes
Change the base suffix from the default value of o=ISP to the appropriate suffix value in each of the ldifs.
Download the file config.zip on the download site: http://docs.iplanet.com/docs/manuals/deladmin.html.
Import the following LDIF files in the order in which they are listed :
Changing Container Names
In Delegated Adminstrator 4.11, the container for user entries was ou=Users; the container for group entries was ou=Depts. In version 4.5, the container for user entries is ou=People; the container for group entries is ou=Groups. Before you can use Delegated Administrator 4.5 with entries created under version 4.11, you must reconcile these differences
Table B-1    Container names
Container type
Administrator 4.11
Delegated Administrator 4.5
. You can do this using one of two methods. You can change the version 4.11 DIT to match the new container names in version 4.5. This is the recommended method. Or you can change the version 4.5 configuration to match the old container names in the version 4.11 DIT. Consider the size and complexity of your DIT in determining which method to use.
Step 1: Change the Version 4.11 Container Names
Since it is not possible to simply rename an entry's DN in the directory, the users & people's container would need to be repopulated if you use this approach.
Change the existing people container (ou=Users) to ou=People.
Change the existing groups container (ou=Dept) to ou=Groups.
Step 2: Change the Version 4.5 Container Names
Change the iDA4.5 configuration entry for the people container object to use ou=Users.
Change the iDA4.5 configuration entry for thegroup container object to use ou=Depts.
In servlets.ldif and main.ldif, change occurances of People to Users; change occurances of Users to Dept.
- This would need to be done in servlets.ldif before importing it in the above step. The following changes would need to be made:
In the ACIs for at the Top level and at the Organization leve, change all occurances of People to Users; change all occurances of Groups to Depts.
Initializing the Object Counters
Delegated Administrator keeps track of the number of objects in the user data tree such as users, groups, organizations, and mailing lists . After manually making changes to the tree, including the steps above to make an existing tree manageable by Delegated Administrator, the object counters must be initialized. This task is typically performed only by Top-level Administrators.
To Initialize the Object Counters
Login as a Top-level administrator and click the Configuration tab.
Click the Initialize Counters button in the Initialize Counters section of the Configuration tab interface. The Initializing Counters window appears and completes the initialization task.
When the task is complete, click Close. If for any reason you do not want to continue the initialization process it may be interupted by clicking the Stop or Stop and Close buttons at the bottom of the Initializating Counters window.
Previous Contents Index Next
Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.
Last Updated May 24, 2001