Novell Home

The How-to Guide for OIDs

Novell Cool Solutions: Feature

Digg This - Slashdot This

Posted: 17 Mar 2004
 

Creating and registering OIDs (unique Organizational IDs to extend the database schema) is not as difficult as you might think - and it's not expensive, either. With unique OIDs, you avoid schema collisions caused by duplicate schema names with different definition structures. And you'll be joining developers to define industry-standard schema to be considered for inclusion into the base schema.

With a few timely tips from Novell Developer Support, you're on your way to simple and effective OIDs. To get the whole story on OIDs, visit the Developer Support page.

Getting Started with OIDs

To get started with your OID, choose one of the following methods

  1. Choose and register a 3- to 8-character OID prefix with Novell, and let Novell supply you the actual OID. There's a small administrative fee.
  2. Get a free OID from ANSI or IANA and register the prefix with Novell.

With your name prefix registration, you can immediately design and implement schema extensions that are unique in NDS.

10 Top Tips for OIDs
  1. For LDAP compatibility, use the following naming scheme: first character = alphabetic; other characters (up to seven more) = alphanumeric.
  2. Keep the prefix lowercase; then you can use mixed case for the name.
  3. Attributes can only be removed if they are not used in a class definition. If you add attributes to Novell base classes, you will not be able to remove them.
  4. Classes can be removed as long as there are no objects instantiated of that class type. Novell base schema cannot be removed.
  5. To add classes and attributes, use the Schema Manager tool in ConsoleOne.
  6. To add multiple extensions at once, use LDAP APIs, eDirectory APIs, or JNDI; or use an LDIF file with the Novell Import Convert Export utility.
  7. Use existing schema where possible. Avoid making unnecessary schema extensions - a large schema can slow performance.
  8. Add the attributes before the classes; otherwise the add will fail because the attributes declared in the class definition aren't in the schema. When you add attributes to an existing class, do a modify schema operation. Do not perform that operation as part of the original add, or it will fail.
  9. Auxiliary classes are newly implemented in NDS 8 and are supported in LDAP. Novell recommends Use auxiliary classes (LDAP-supported, new in eDirectory 8) whenever possible, especially when adding attributes to base schema classes. An auxiliary class is a collection of attributes that does not require class inheritance.
  10. Grab a Directory OID/Prefix Registration Form to get started!


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell