Extending the ADAM Schema






Extending the ADAM Schema

Problem

You want to extend the ADAM Schema with new classes or attributes.

Solution

Using a command-line interface

To extend the ADAM Schema from the command-line, you'll need to create an LDIF file containing the necessary schema extensions, and then import it using the LDIFDE command, or use a tool like AdMod to perform the changes. ADAM comes with a number of such LDIF files pre-installed that you can import during the ADAM installation process. If you did not import these files during installation, you can do so after the fact using the following syntax:

	> ldifde -i -f <driveletter>:\<pathname>\contact.ldf s<servername>:<portnumber>-k
	-j . -c "CN=Schema,CN=Configuration" #schemaNamingContext

Discussion

The schema that you receive when you install ADAM contains a subset of the classes and attributes that exist in the Active Directory Schema. You have the same ability to extend the schema in ADAM as you do in AD, which means that you can expand and modify the schema to be the same as the AD Schema, or to match any changes made by your third-party or home-grown applications. Because of this, ADAM is a great place to test potential schema modifications that you want to make in Active Directory. Because the schema extension process works the same in both AD and ADAM, and because you can easily install, uninstall, and reinstall ADAM instances, you can use ADAM to quickly test new extensions, tweaking the definitions until you get exactly what you want.

Every instance of ADAM will have at least two partitions: the Configuration partition and the Schema partition; you can create additional application partitions during or after installation as described in Chapter 18. Similar to the Active Directory Schema NC, the ADAM Schema partition contains definitions of classes and attributes that can be used to create objects within a particular ADAM instance. An ADAM Schema is unique to an individual ADAM instance; changes to the schema in one instance will not affect the schema in other, separate instances. ADAM comes with a number of pre-configured LDIF files that you can import to create common object types such as user, contact, and inetorgperson objects. You can import these LDIF files during the initial creation of an ADAM instance as well as after the instance has been created.

Using a command-line interface

When updating the ADAM Schema, be sure to use the version of ldifde that came with ADAM rather than any earlier versions of the utility.

See Also

Recipe 19.2, MSDN: Adding User Classes [ ADAM], MSDN: Adding Contact Classes [ ADAM], MSDN: Extending the Active Directory Application Mode Schema [ADAM], and Chapter 18 of Active Directory, Third Edition, by Joe Richards et al. (O'Reilly)



 Python   SQL   Java   php   Perl 
 game development   web development   internet   *nix   graphics   hardware 
 telecommunications   C++ 
 Flash   Active Directory   Windows