Home
IBM® Domino 10.0.1 Documentation
Welcome to the IBM® Domino 10.0.1 Administrator Help.
Configuring
Use this information to configure an IBM® Domino® network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters. Also use this information to set up IBM iNotes® on a server using Domino Off-Line Services (DOLS).
Configuring directory services
This section describes how to plan, set up, and use IBM® Domino® directory services.
The Domino® Directory
The Domino® Directory, which some previous releases referred to as the Public Address Book or Name and Address Book, is a database that Domino creates automatically on every server. The Domino Directory is a directory of information about users, servers, and groups, as well as custom entries you may add. Registering users and servers in a domain automatically creates corresponding Person documents and Server documents in the Domino Directory for the domain. These documents contain detailed information about each user and server.
The Domino® Directory template
The default Domino® Directory template (PUBNAMES.NTF) controls the appearance and functionality of the Domino Directory database (NAMES.NSF). Domino uses the forms and settings in the default Domino Directory template to control features -- for example, mail, server tasks, and access control -- and to store critical information that manages server connections, mail routing, and system configuration.
Using the Domino® Directory to extend the LDAP schema
To add schema elements to the Domino® LDAP schema, you can create forms and subforms in the Domino Directory, or you can use the Domino LDAP Schema database (SCHEMA.NSF).
Using the Domino® Directory to create a new LDAP structural object class
You can add a form and associated subforms to the Domino® Directory to define a new LDAP structural object class in the LDAP schema and to enable documents created from the form to be LDAP-accessible. The preferred method for extending the schema is to use the Domino LDAP Schema database, however. Use the Domino Directory to extend the schema only if Notes® or Web users require access to the new entries defined by the schema elements through documents in the directory.
Creating and inserting a $xxxInheritableSchema subform
After you create a form to define a new structural object class, create an associated $xxxInheritableSchema subform and insert it into the form. The $xxxInheritableSchema subform defines the attributes for the structural object class.

Creating and inserting a $`xxx`InheritableSchema subform

After you create a form to define a new structural object class, create an associated $xxxInheritableSchema subform and insert it into the form. The $xxxInheritableSchema subform defines the attributes for the structural object class.

Before you begin

Make sure that you are working in a copy of the IBM® Domino® Directory template (for example RENOVATIONSNAMES.NTF) and that you have Designer or Manager access in the ACL.

Procedure

From IBM Domino Designer, open RENOVATIONSNAMES.NTF.
Do the following to copy the contents of the $countryInheritableSchema subform into a new subform:

Important: Do not select the $countryInheritableSchema subform and use copy and paste to copy it.
1. In the navigation pane, select Shared Elements and then Subforms.
2. Open the $countryInheritableSchema subform, choose Edit > Select All, then Edit > Copy.
3. Close the $countryInheritableSchema subform.
4. With Subforms still selected, right-click New Subform. For the form name, type $xxxInheritableSchema, where xxx is the name of the new structural object class created previously, for example, $renovationsPrinterInheritableSchema. Click OK.
5. Choose Edit > Paste.
Do the following to specify the properties for the new subform:
1. With the new subform open, choose Design > Subform Properties.
2. Deselect the Options property Render pass through HTML in Notes.
3. Leave the other properties the same, and close the Subform Properties box.
On the Mandatory tab, do the following:
1. Delete the field OfficeCountry and its label. Do not delete the $dspType field and label.
2. Choose Create > Field.
3. Next to the Name property, specify FullName.
4. Next to the Type property, select Names.
5. Close the Field box.
6. Select Input Validation in the Object pane, and enter the following formula:
```
@V2If(FullName = ""; @Failure("FullName is required"); @Success)
```
Optional: On the Optional tab, delete the searchGuide field and its label, and optionally delete the comment field and its label.
Leave the Operational tab as is.
Define the mandatory and optional attributes for the new structural object class in the new InheritableSchema subform.
Do the following to remove the $countryExtensibleSchema subform from the new InheritableSchema subform:
1. On the Extensible tab of the new InheritableSchema subform, place the cursor the equivalent of one line down to select the $countryExtensibleSchema subform.
2. Verify that the $countryExtensibleSchema subform is selected. Click Edit > Delete to remove the $countryExtensibleSchema subformfrom the new InheritableSchema subform.
Save and close the new InheritableSchema subform.
Do the following to insert the new InheritableSchema subform into the form created to define the structural object class:
1. From Domino Designer, open RENOVATIONSNAMES.NTF.
2. In the navigation pane, select Forms and open the form you created previously -- for example, renovationsPrinter.
3. Position the cursor between the form name and the Type, Owner, LocalAdmin, and DocumentAccess fields.
4. Choose Create > Resource > Insert Subform, select the InheritableSchema subform you created -- for example $renovationsPrinterInheritableSchema -- and click OK.
Save and close the form.

What to do next

Complete the procedure Creating and inserting an $xxxExtensibleSchema subform.