iManager Framework API

The iManager Framework API consists of iManager Packages and AdminNamespace Packages.

See:
          Description

iManager Packages
com.novell.emframe.dev The dev package contains classes needed for plug-in writers to write plug-ins to iManager.
com.novell.emframe.dev.authenticator The authenticator package has interfaces and objects used to write your own iManager Authenticator.
com.novell.emframe.dev.config The config package handles all configuration settings used by the iManager server and any modules or tasks.
com.novell.emframe.dev.dataTable The dataTable package contains Java classes to use in creating a simpleTable as part of the iManager JSP tag library (iman.tld).
com.novell.emframe.dev.rights The rights package has Java objects to represent all eDirectory rights of objects and attributes of those objects.

 

AdminNamespace Packages
com.novell.admin.common.exceptions Exceptions and Errors generated when using the AdminNamespace.
com.novell.admin.ns General classes and interfaces for accessing eDirectory - These classes are naming independent and can operate over both NDAP and LDAP naming access methods.
com.novell.admin.ns.ldap Classes for accessing eDirectory using LDAP naming.
com.novell.admin.ns.nds Classes for accessing eDirectory using NDAP naming, the Novell Directory Service Namespace, and some general purpose attribute convenience routines.
com.novell.application.console.snapin Framework classes and default implementations for the AdminNamespace.

 

The iManager Framework API consists of iManager Packages and AdminNamespace Packages.

iManager Packages

Developers writing plug-ins for iManager will need to use the iManager Packages and extend the appropriate Java classes. A plug-in consists of Business Logic, Presentation Logic, and a Plug-in Descriptor.

Business Logic

Presentation Logic

Plug-in Descriptor

All plug-ins will need at least a Plug-in Descriptor and Business Logic. Only plug-ins that present a User Interface will need Presentation Logic.

There are several different types of plug-ins. The Business Logic needs to extend different classes depending upon the plug-in type:

Note on deprecated classes: If you are using classes outside of the dev package in com.novell.nps, these calls have all been depricated and replaced with calls inside of the dev package. Please convert your code so all references to com.novell.nps have been removed.

AdminNamespace Packages

Developers wanting to connect over NDAP or LDAP to a directory can use the AdminNamespace Packages. The AdminNamespace Packages make it so a plug-in can communicate over NDAP or LDAP with the same plug-in Java code without a complete rewrite of the plug-in. As long as the plug-in does not do parsing of the object name, their code should work over both protocols. However, if their plug-in does do parsing of the object name or other protocol specific work, the plug-in can either be written twice or have conditionals whenever protocol specific handling is required.

Plugins use the AuthenticationBroker to handle making connections to the directory over the various protocols or to get the credentials used to login to iManager to make their own single sign-on connections to other back end data sources.



API Documentation Copyright © 1998-2004 Novell, Inc. All rights reserved.
NDS is a registered trademark of Novell, Inc. in the United States and other countries.
Generated September 2 2004 0111.