software

How to Bundle Active Directory Application Mode

Daniel Fleshbourne   on 01 March 2004 - 21:48 · 5 comments & 400 views

Advertisement (Why?)
Overview
Active Directory Application Mode (ADAM) is a new mode of the Active Directory® directory service that is designed to meet the needs of the following: Line-of-business applications that require a dedicated Lightweight Directory Access Protocol (LDAP) data store, E-commerce applications that require simple LDAP authentication support, and enterprise environments that require an application directory that is separate from their network operating system (NOS) infrastructure directory.

Application developers whose directory-enabled applications require a dedicated LDAP data store now have the option of bundling ADAM with their custom applications. In addition, application developers have the option of including the installation of ADAM as a part of the installation process of their custom applications. This document describes how to distribute ADAM with a custom application by bundling ADAM Setup within the setup program of a custom application.

System Requirements:
  • Windows Server 2003
  • Microsoft Word or Word Viewer

    Download: How to Bundle Active Directory Application Mode with Your Directory-enabled Application
    View: Microsoft Windows Server™ 2003 Home Page


  • You can get Winamp 5 at: www.winamp.com.
    You can get WindowBlinds at: www.windowblinds.net SkinStudio (which makes skins) at www.skinstudio.net (SkinStudio is free).
    You can get IconPackager at IconZone.com

    Post a comment · Send to friend Comments · There are 5 additional comments
    #1 dougkinzinger on 02 Mar 2004 - 12:53
    I have a lot of customers, but I still can't for the life of me figure out who would benefit from ADAM, as opposed to full-blown AD....anyone have any examples?
    #2 envision on 02 Mar 2004 - 18:20
    dougkinzinger: i interpreted that differently...

    My interpretation is not that ADAM is meant to replace AD in any way.. you don't compare them as they are not the same thing.
    ADAM basically allows your application to store data in the active directory and I am guessing ADAM will make the LDAP links possible between AD and your application.

    Or something ...dunno, am tired!
    #3 dougkinzinger on 02 Mar 2004 - 18:22
    Ah, yes, well, if that's the case, then great, I can appreciate that. I suppose I should read the documentation!
    #4 envision on 02 Mar 2004 - 18:25
    hahaha, yeah I should read it too, not completely clear, but... nah i am too lazy
    #5 rogerroger on 02 Mar 2004 - 19:32
    It is for when you use a active directory aware product in a non-AD environment, i.e. Linux, Novell, etc. You can use it in an existing AD environment, but it is of lessor use. I have seen it used in an extranet situation when employee data from one company is queried by an outside entity. It is useful in terms of hr data for external benefit providors (since you control how much deatil goes into the accounts), but other than that, I don't know where else to use it.

    Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!

    Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.

    Advertisement (Why?)