directory-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Richard Mixon <>
Subject Re: [ApacheDS] [Studio]
Date Sun, 15 Sep 2013 23:11:24 GMT

OK - I understand a bit more about the problems I encountered and why.
Please bear with my analysis - there is a point to it.

First - yes, there are some places in the documentation that are not clear
or that have not been updated to the current releases of the product.

Second, being such a newbee with Apache DS and LDAP to some extent, I just
simply overlooked some items which in retrospect are quite clear. For
example, as someone suggested when you create a new  partition the context
entry is now created for you. Yes it is  - it's checked by default, but you
do need to changed the default configuration for the context entry.

I have the snapshots and documentation to easily expand the last part of
section 1.5, beginning with "The sample data (Sailors of the seven seas)"
to be the more comprehensive step-by-step. It would be based upon
installing Apache Directory Studio, creating the server in studio and all
the steps to successfully load and browser the sample data.

Since the entire use case uses Apache Directory Studio, not just Apache DS,
should the example go in the Apache Directory Studio documentation? I did
not see a clear place in the user guides as they are divided according to
studio component (LDAP Browser, LDIF Editor, etc).

Maybe there is some place I'm overlooking - a wiki, or other place.

I'll wait to hear then submit the JIRA with the documentation patch.

Thank you - Richard

On Fri, Sep 13, 2013 at 11:24 PM, Emmanuel Lécharny <>wrote:

> Le 9/14/13 6:43 AM, Richard Mixon a écrit :
> > Emmanuel,
> > Thank yo u - I ended up doing something similar that worked, after
> starting
> > over with a default config.ldif
> >
> > 1. Created a partition with ID of sevenSeas and Suffix "dc=sevenSeas"
> > 2. After restarting the server, right-clicked on the partition and
> created
> > an entry with "o=sevenSeas". BTW, when you do this and select New, you
> are
> > given options to create a New Entry or a New Context Entry. I would have
> > thought Context Entry was the right choice, but just the simple Entry is
> > what worked.
> The ContextEntry is associated with the partition, ie with dc=sevenSeas.
> Here, you have created another entry which DN is
> o=sevenSeas,dc=sevenSeas. This is a plain new entry, not a Context entry.
> I *think* that whe you create the partition, the context entry is now
> automatically created (to be checked), and if so, we have to fix the
> documentation to reflect this feature.
> > 3. Afterwards after adding the following entry to the top of
> > apache-ds-tutorial.ldif it successfully imported:
> >
> > dn: o=sevenSeas,dc=sevenSeas
> > o: sevenSeas
> > objectClass: top
> > objectClass: organization
> > description: The context entry for suffix o=sevenSeas
> >
> > Thank you all for you help.
> >
> > I believe it would help a lot of LDAP nubies if the the tutorial recipe
> was
> > a bit more precise for importing the example/tutorial.
> >
> > Is there a way to contribute some corrections/clarifications to these
> links?
> >
> >
> >
> > I would be happy to do so.
> They are plain text document, using markdown. They are available at
> .
> Any patch on those files (and that can include fixes to the bad english
> used) is very welcomed (the best way to submit patches is to create a
> JIRA - see - and to
> attach a diff to it).
> Many thanks !
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny

Richard Mixon
Custom Computer Creations, L.L.C.
mobile: (480) 577-6834 office: (480) 614-3442
email: <>
Microsoft Partner ID: 1263725
The messages and documents transmitted with this notice contain
confidential information belonging to the sender. If you are not the
intended recipient of this information, you are hereby notified that any
disclosure, copying, distribution or use of the information is strictly
prohibited. If you have received this transmission in error, please notify
the sender immediately.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message