Re: ADAM:Delete an DN - What should happen?
anonymous_at_discussions.microsoft.com
Date: 08/06/04
- Next message: Eoin Mooney: "Re: ADAM:Delete an DN - What should happen?"
- Previous message: st: "error 1810"
- In reply to: Dmitri Gavrilov [MSFT]: "Re: ADAM:Delete an DN - What should happen?"
- Next in thread: Dmitri Gavrilov [MSFT]: "Re: ADAM:Delete an DN - What should happen?"
- Reply: Dmitri Gavrilov [MSFT]: "Re: ADAM:Delete an DN - What should happen?"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 6 Aug 2004 02:29:53 -0700
Hi Dimitri,
Thanks for the response , I understand to a point what you
are saying , there is one sentence which I cannot
understand
"It will not be garbage collected until this outstanding
reference exists"
Does this mean it will be garbage collected eventually ?
What do you mean by "until this oustanding reference
exists"
Thanks
Eoin
>-----Original Message-----
>What you have is called "DN value" or "DN reference".
When you delete the
>destination, the reference is not deleted, and continues
to point to the
>deleted object. It will not be garbage collected until
this outstanding
>reference exists.
>
>If you want to have the reference deleted from the source
when the target is
>removed, then you need to make your attribute a "linked"
attribute. An
>example of a linked attribute is "member". When you
delete a user, it is
>automatically removed from all groups that he was a
member of.
>
>What distinguishes a linked DN valued attribute from a
non-linked one is the
>presence of linkId in the attribute definition. It should
be an even number
>for forward links. With linked attributes, it is possible
to introduce the
>"backlink" (i.e. memberOf). It is a "computed" attribute.
Whenever you add a
>value to the link attribute (i.e. add a member to a
group), the backlink
>automagically appears on the dest pointing back to the
source (i.e. memberOf
>is updated on the user). The backlink must be a dn-valued
attribute with
>linkId == linkId_of_link_attribute + 1.
>
>I don't know if we have a process for registering
linkIds. If you plan to
>ship your app to other people, make sure to choose some
random linkId value
>(in dword range), so that it does not collide with
somebody else's schema
>extension.
>
>--
>Dmitri Gavrilov
>SDE, Active Directory Core
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>Use of included script samples are subject to the terms
specified at
>http://www.microsoft.com/info/cpyright.htm
>
>"Eoin Mooney" <anonymous@discussions.microsoft.com> wrote
in message
>news:0b5c01c47afc$7d26ab50$a601280a@phx.gbl...
>> Hi there,
>>
>> I have added a value into an attribute that points to
>> another area of ADAM
>>
>> e.g
>> l=xxxx,OU=Servers,OU=ice,O=NN,DC=NN,DC=COM is the
>> actual object in ADAM , I build up a string based on the
>> L= value passed to me and add it to an attribute in
>> another object.
>>
>> Initially I receive a name,I then make up the
>> distinguished name and then pass the string into the
>> Distinguished Name attribute of a organizationalUnit.
>>
>> The reason I do this is so when the actual DN is deleted
>> in the other area of ADAM the attribute that holds the
>> Distinguished Name entry will be removed also without
>> extra coding to tidy ADAM.
>>
>> Tests have shown this works, I delete the actual object
in
>> ADAM and the attribute with [for want of a better word]
>> the pointer to this object cannot be seen in our
>> application when read. But I used ADSIEdit to look at
the
>> location to determine if the entry was actually gone
and I
>> found this
>>
>>
>> L=ncc500\0ADEL:7032xxxx-xxxxxx-xxxxxx,CN=Deleted
>> Objects,DC=Nortelnetworks,dc=com
>>
>> This seems to allow ADAM to ignore this entry even
though
>> it is still in the attribute. I then added the actual
>> object back in and this entry went back to the normal
>> l=xxxx,OU=Servers,OU=ice,O=NN,DC=NN,DC=COM and our
>> application could see it again.
>>
>> My question is :
>>
>> Will this entry [L=ncc500\0ADEL ....] disappear
eventually
>> if I do not re-introduce the object?
>> What I am worried about is if we add and delete many
times
>> then the attribute will be messed up with these entries
>> even though they seem to have no adverse effect [that I
>> know of]
>>
>> The attribute that holds these entries is below
>>
>> dn: CN=iceAssociatedServers,CN=Schema,CN=Configuration
>> changetype: add
>> objectClass: attributeSchema
>> objectCategory: CN=Attribute-
>> Schema,CN=Schema,CN=Configuration
>> adminDisplayName: iceAssociatedServers
>> cn: iceAssociatedServers
>> lDAPDisplayName: iceAssociatedServers
>> attributeID: 1.3.6.1.4.1562.35.53.2.105
>> attributeSyntax: 2.5.5.1
>> omSyntax: 127
>> omObjectClass:: KwwCh3McAIVK
>> isSingleValued: FALSE
>>
>> and I add it to
>>
>> dn: CN=iceServer,CN=Schema,CN=Configuration
>> changetype: modify
>> add: mayContain
>> mayContain: iceAssociatedServers
>>
>
>
>.
>
- Next message: Eoin Mooney: "Re: ADAM:Delete an DN - What should happen?"
- Previous message: st: "error 1810"
- In reply to: Dmitri Gavrilov [MSFT]: "Re: ADAM:Delete an DN - What should happen?"
- Next in thread: Dmitri Gavrilov [MSFT]: "Re: ADAM:Delete an DN - What should happen?"
- Reply: Dmitri Gavrilov [MSFT]: "Re: ADAM:Delete an DN - What should happen?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|