Re: ADAM Partitions on Separate Servers

Hi

no your usage here is fine I think.
So when you say root and branch is that like:

o=corp
l=sub1,o=corp

where both are partitions (naming context heads) or is l=sub1 just an
object instance in the o=corp partition?

Clearly you can create two independent ADAM instances but if need
to pick up searches from say o=corp for both subsidiaries then it has to
be a subtree search with a single tree or you could create a separate
partition for the later subsidiary on a second ADAM instance and then
on the original ADAM instance create a cross reference for that partition.

The problems with a cross reference are:

that it will generate an LDAP referral for the client and the client will
have to be able to expect/handle that (chase the referral)

and further referral chasing crosses security boundaries so that, say,
if the account that you are accessing the initial ADAM instance with
is an account within that ADAM instance then account will not be valid
in the second ADAM instance

Does that help?

This sounds like a large directory are you replicating it?

Thanks
Lee Flight



"drm" <don.mai@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ea6834ac-0207-447a-89f7-5e33f9742603@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Thanks Lee,

Perhaps partition is the wrong word. The company I work for consists
of multiple subsidiaries. We created an ADAM instance with a
corporate root. Under that root there is a branch for one of the
subsidiaries. We would like to create another branch for a second
subsidiary. Due to the size of the first branch (over 7m records
using 22.5 gb), I was wondering if I can, and how would I, put the new
branch on a separate server. Most of the queries will be from the
subsidiary level down but there may be cases where the queries will be
at the corporate level.


.

Relevant Pages

  • Re: ADAM Partitions on Separate Servers
    ... partition for the later subsidiary on a second ADAM instance and then ... on the original ADAM instance create a cross reference for that partition.. ...    that it will generate an LDAP referral for the client and the client will ... of multiple subsidiaries. ...
    (microsoft.public.windows.server.active_directory)
  • Re: ADAM Partitions on Separate Servers
    ... Clearly you can create two independent ADAM instances but if need ... partition for the later subsidiary on a second ADAM instance and then ... on the original ADAM instance create a cross reference for that partition. ... of multiple subsidiaries. ...
    (microsoft.public.windows.server.active_directory)
  • Error in creating ADAM application partition
    ... I already created an application partition when I installed ADAM instance. ... After the new application directory partition is added, ... Error 0x2073 An attempt was made to add an object using an RDN that is not ...
    (microsoft.public.windows.server.active_directory)
  • Re: ADAM and Directory Partitions
    ... The schema and configuration are common to any number of ADAM instances ... within the same configuration set. ... identified with the data you've provided; scale in terms of partition ... partition in the same adam instance but have another set of attributes ...
    (microsoft.public.windows.server.active_directory)
Loading