You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by fe...@apache.org on 2011/12/08 21:33:53 UTC
svn commit: r1212094 - in
/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence:
./ basic-security/ how-to-begin/ how-to-begin/basic_configuration_tasks/
images/ managing-data-within-your-directory/ taking-advantage-of-apacheds/
Author: felixk
Date: Thu Dec 8 20:33:52 2011
New Revision: 1212094
URL: http://svn.apache.org/viewvc?rev=1212094&view=rev
Log:
Start moving basic user guide from confluence, 1. Chapter (DIRSERVER-1678)
Added:
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/basic-security/
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin.confluence
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/about_the_sample_configurations_and_sample_directory_data.confluence
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks.confluence
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/about_configuration_of_a_standalone_apacheds.confluence
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/adding_your_own_partition_resp_suffix.confluence
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/changing_the_admin_password.confluence
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/configure_logging.confluence
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/installing_and_starting_the_server.confluence
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/some_background_directories_directory_services_and_ldap.confluence
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/what-apache-directory-server-is.confluence
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/apache_directory_studio.png (with props)
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/copy-entry-subtree-depth-in-directory-studio.PNG.jpg (with props)
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/partitionsuffix-sevenseas-in-directory-studio.PNG.jpg (with props)
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/properties_root_dse.png.jpg (with props)
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/sample_data_bug_structure.png (with props)
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/managing-data-within-your-directory/
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/taking-advantage-of-apacheds/
Modified:
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/book.txt
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/NewLDAPConnection1.png
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/NewLDAPConnection2.png
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/connectionProperties.png
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/entryEditor.png
directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/passwordEditor.png
Modified: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/book.txt
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/book.txt?rev=1212094&r1=1212093&r2=1212094&view=diff
==============================================================================
--- directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/book.txt (original)
+++ directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/book.txt Thu Dec 8 20:33:52 2011
@@ -1,6 +1,16 @@
-example.confluence
+#example.confluence
preface.confluence
introduction.confluence
-how-to-begin-chapter.confluence
-how-to-begin-section.confluence
-how-to-begin-subsection.confluence
+how-to-begin.confluence
+how-to-begin/what-apache-directory-server-is.confluence
+how-to-begin/some_background_directories_directory_services_and_ldap.confluence
+how-to-begin/installing_and_starting_the_server.confluence
+how-to-begin/about_the_sample_configurations_and_sample_directory_data.confluence
+how-to-begin/basic_configuration_tasks.confluence
+how-to-begin/basic_configuration_tasks/about_configuration_of_a_standalone_apacheds.confluence
+how-to-begin/basic_configuration_tasks/changing_the_admin_password.confluence
+how-to-begin/basic_configuration_tasks/adding_your_own_partition_resp_suffix.confluence
+how-to-begin/basic_configuration_tasks/configure_logging.confluence
+#managing-data-within-your-directory
+#basic-security
+#taking-advantage-of-apacheds
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin.confluence
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin.confluence?rev=1212094&view=auto
==============================================================================
--- directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin.confluence (added)
+++ directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin.confluence Thu Dec 8 20:33:52 2011
@@ -0,0 +1 @@
+h1. How to begin
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/about_the_sample_configurations_and_sample_directory_data.confluence
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/about_the_sample_configurations_and_sample_directory_data.confluence?rev=1212094&view=auto
==============================================================================
--- directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/about_the_sample_configurations_and_sample_directory_data.confluence (added)
+++ directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/about_the_sample_configurations_and_sample_directory_data.confluence Thu Dec 8 20:33:52 2011
@@ -0,0 +1,68 @@
+h2. About the sample configurations and sample directory data
+
+This section describes basic parameters used throughout the examples in this guide. It also introduces the sample directory "Sailors of the seven seas", and other requisites you need.
+
+{toc:type=list|minLevel=2|maxLevel=2}
+
+h3. Basic server parameters
+
+In the following sections we assume that you will install, configure and run Apache Directory Server on a host with the following host name using the parameters given in the following table:
+
+|| Parameter name || Parameter value ||
+| Hostname | zanzibar |
+| LDAP Port | 10389 |
+| Suffix ("Base DN") | o=sevenSeas |
+| Admin user DN | uid=admin,ou=system |
+| Admin user password | secret |
+
+Before you start playing with the data make sure that you have added a partition with the suffix o=sevenSeas to the server. How to do this is described [here|1.5. Basic configuration tasks#Adding your own partition (suffix)].
+In order to increase recognition, all examples of the Basic User's Guide use these values. Adjust them to your needs (especially the password).
+
+h3. LDAP Clients
+
+LDAP is a client/server protocol. Hence you need an LDAP client to connect remotely to the Apache Directory Server (or at least the directory part of it, to be precise). There are different options here. Because the protocol is standardized, you may use every LDAP compliant client. This is comparable to HTTP, where you can use each web browser to communicate with virtually each web server, and totally different to relational databases. The latter have a (more or less) standardized query language (SQL), but vendors tend to use individual network access protocols. In practice, the LDAP situation is even better than HTTP, because there were no LDAP browser wars ...
+
+Many software components may act as an LDAP client. Normally they use LDAP libraries to connect. In the following sections you meet LDAP clients with GUI and LDAP command line tools. Some Java programming examples which takes advantage of JNDI are provided as well. Note that the Apache Directory Project provides a powerful GUI tool called [Apache Directory Studio|http://directory.apache.org/studio/|directory.apache.org], which you should definitely try out. It will be the preferred LDAP UI tool option in this guide.
+
+!images/apache_directory_studio.png!
+
+In later sections you will learn how E-Mail clients like Mozilla Thunderbird and application servers like Apache Tomcat connect to Apache Directory server, either to use the data stored in the directory (e.g. mail addresses) or to perform authentication and authorization.
+
+Recapitulating the Basic User's Guide describes connecting to the server with tools provided by ApacheDS as well as third party products. In all cases the examples will use the connection data depicted above (_ldap://zanzibar:10389/o=sevenSeas_)
+
+h3. The sample data (Sailors of the seven seas)
+
+The file [^sample_data_bug.ldif] contains some sample data, which is used in the following sections. It is a text file in the so called *LDIF* format. LDIF stands for LDAP Data Interchange Format. It is widely adopted in the LDAP world and standardized in [RFC 2849|http://www.faqs.org/rfcs/rfc2849.html|www.faqs.org]. Therefore you are able to import our sample data into other directory solutions as well, not only into Apache Directory Server.
+
+The sample directory tree contains entries for persons and groups. These are structured in sub trees (ou=people and ou=groups), see image below. The person entries describe sailors (historic and fictional), the group entries bundle them. An example for a group is the ship crew of HMS Bounty.
+
+!images/sample_data_bug_structure.png!
+
+This snippet of the file represents a single entry, just to give you an impression of how LDIF files look like.
+{noformat}
+...
+# Entry for Fletcher Christian
+#
+dn: cn=Fletcher Christian,ou=people,o=sevenSeas
+cn: Fletcher Christian
+objectClass: top
+objectClass: person
+objectClass: organizationalPerson
+objectClass: inetOrgPerson
+sn: Christian
+givenName: Fletcher
+description: Lieutenant Fletcher Christian
+manager: cn=William Bligh,ou=people,o=sevenSeas
+...
+{noformat}
+
+There are different ways to import the data. Generally perform the following steps:
+
+* Download and install the server, described im [1.3. Installing and starting the server]
+* Configure a partition for the sample date, described in [1.5. Basic configuration tasks]
+* Import the data, for instance with the [2.1.2. ApacheDS tools]
+
+h3. Resources
+
+* [RFC 2849|http://www.faqs.org/rfcs/rfc2849.html|The LDAP Data Interchange Format (LDIF)] The LDAP Data Interchange Format (LDIF) -- Technical Specification
+* [Apache Directory Studio|http://directory.apache.org/studio/|directory.apache.org] A powerful Eclipse based LDAP browser and directory client
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks.confluence
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks.confluence?rev=1212094&view=auto
==============================================================================
--- directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks.confluence (added)
+++ directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks.confluence Thu Dec 8 20:33:52 2011
@@ -0,0 +1 @@
+h2. Basic configuration tasks
\ No newline at end of file
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/about_configuration_of_a_standalone_apacheds.confluence
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/about_configuration_of_a_standalone_apacheds.confluence?rev=1212094&view=auto
==============================================================================
--- directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/about_configuration_of_a_standalone_apacheds.confluence (added)
+++ directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/about_configuration_of_a_standalone_apacheds.confluence Thu Dec 8 20:33:52 2011
@@ -0,0 +1,21 @@
+h3. Changing the server port for LDAP
+
+Changing the LDAP port is a good example for adjusting the existing configuration as introduced in the last section. By default the LDAP server listens on port 10389. It is quite common to run LDAP on 389, which is the well-known port for this protocol. Of course other options are imaginable as well.
+
+Just pick the following lines within the _server.xml_ file
+
+{code}
+<ldapServer id="ldapServer"
+ ipPort="10389"
+ allowAnonymousAccess="false"
+ ...>
+ ...
+</ldapServer>
+{code}
+
+and change the value of _ipPort_ to your needs. You have to restart the server afterwards in order to take this change effect.
+
+{note}
+Due to traditional Unix security restrictions, ports less than 1024 were "trusted". Thus on a Unix-System, a non-root process must listen on a port greater than 1023.
+{note}
+
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/adding_your_own_partition_resp_suffix.confluence
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/adding_your_own_partition_resp_suffix.confluence?rev=1212094&view=auto
==============================================================================
--- directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/adding_your_own_partition_resp_suffix.confluence (added)
+++ directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/adding_your_own_partition_resp_suffix.confluence Thu Dec 8 20:33:52 2011
@@ -0,0 +1,154 @@
+h3. Adding your own partition resp. suffix
+
+This section describes how to add your own data partition.
+
+{toc:type=list|minLevel=2|maxLevel=2}
+
+h4. What are partitions?
+
+In ApacheDS entries are stored in partitions. Each partition contains a complete entry tree, also referred to as a DIT. Multiple partitions may exist and the entry trees they contain are disconnected from each other, meaning that changes to entries in partition _A_ would never affect entries in partition _B_. The entries in a particular partition are stored below some naming context called the partition suffix.
+
+The default implementation of partitions is based on [JDBM|http://jdbm.sourceforge.net/|jdbm.sourceforge.net] B+Trees (but it's possible to add custom partition implementations). The ApacheDS default configuration contains a a data partition with the suffix "dc=example,dc=com". The image below shows the suffixes of a freshly installed ApacheDS within Apache Directory Studio.
+
+!images/partitions_in_studio_after_install.png!
+
+The schema subsystem and ApacheDS itself store their information in special partitions, "ou=schema" and "ou=system" respectively.
+
+h4. Minimal partition definition
+
+For the examples in the following sections, we want to add a partition with the suffix "o=sevenSeas". This requires editing of the server configuration stored in the ApacheDS server, and injecting a first entry, associated with the root of this partition (here, "o=sevenseas").
+
+{info:title=Note}
+The way, ApacheDS handles configuration has changed with version 2.0. The configuration is now completely held in the server and can be edited with any LDAP browser or even by hand, using a text editor. However, using an LDAP browser is much more comfortable and is also recommended.
+{info}
+
+Open Apache Directory Studio or any other LDAP browser and connect to your ApacheDS server. Browse to the entry {{ou=partitions,ou=config}}. Below there, you will find all currently configured partitions in your server. Duplicate the {{example}} partition by copying the entry and pasting the whole _subtree_ (see image below).
+
+!images/copy-entry-subtree-depth-in-directory-studio.PNG.jpg|thumbnail!
+
+In the copy/paste dialog, titled "Select copy strategy", choose to _rename the entry and continue_ and set the name according to our example to "sevenseas". Click/doubleclick (depends on your settings or your LDAP browser) your newly created partition to open it for editing. Look for the attribute {{ads-partitionsuffix}} and modify its value to {{o=sevenseas}}. The new partition has now been configured - time to restart your server!
+
+Before you can use the partition (e.g. adding entries), you have to add a context entry. Connect to ApacheDS again. You can currently see the partition only in the Root DSE. The picture below shows the Properties dialog of Directory Studio for the Root DSE element after connecting to an ApacheDS instance configured like above.
+
+!images/properties_root_dse.png.jpg|thumbnail!
+
+Right-click the {{Root DSE}} entry and create a new _context entry_ below it. Select {{dcObject}} and {{organization}} as object classes. On the next dialog page, you will be asked for a distinguished name for the context entry. In the dropdown list the new partition suffix {{ou=sevenseas}} should have become available (image below). Select it and move on to the next dialog page.
+
+!images/partitionsuffix-sevenseas-in-directory-studio.PNG.jpg|thumbnail!
+
+There, enter the value "Pirates of the Seven Seas, Inc." into the {{dc}} attribute. That's it! Now you have added a new suffix and created a context entry for it. You are now ready to fill the new partition with data. As an alternative for adding the context entry manually, you can load it with your LDIF data - if you plan to load LDIF data into your partition anyway. Simply provide the context entry (the "root" of your partition) as a first data set. In our example it might look like this:
+
+{code}
+dn: o=sevenSeas
+o: sevenSeas
+objectClass: top
+objectClass: organization
+description: The context entry for suffix o=sevenSeas
+{code}
+
+It is also possible to import a file to ApacheDS which only contains such an entry, of cause. Here is an example on how to procede for the seven seas:
+
+In the LDAP Browser of Directory Studio, right click on the DIT entry and select "Import -> LDIF Import...". A file selections dialog appears. Browse to the LDIF file and click Finish. The entry (or entries, if you provide more of them) will be added to to partition.
+
+The following image depicts the partitions after reconnecting with Apache Directory Studio (_LDAP Browser_ view).
+
+!images/partitions_in_studio_after_adding.png!
+
+h5. Loading the context entry automatically on startup
+If you don't want to launch Apache Studio, or to inject the LDIF file using a command line tool, you can also tell the server to load the file when it will be laucnhed the first time. Just create an ldif file containing the context entry, and add some tag into the _server.xml_ file. For instance, you have created the *sevenSeasRoot.ldif* file containing
+
+{code}
+# SevenSeas root context entry
+dn: o=sevenSeas
+o: sevenSeas
+objectClass: top
+objectClass: organization
+description: The context entry for suffix o=sevenSeas
+{code}
+
+Now just modify the _server.xml_ file to add this line :
+
+{code}
+ ...
+ <apacheDS id="apacheDS"
+ synchPeriodMillis="15000"
+ allowAnonymousAccess="false">
+
+ <directoryService>#directoryService</directoryService>
+
+ <!-- We load the SevenSeas root context entry here -->
+ <ldifDirectory>sevenSeasRoot.ldif</ldifDirectory>
+ ...
+{code}
+
+The contextEntry will be loaded when the server will be started the first time.
+
+h4. More configuration options for a JDBM partition
+
+Here is a list of the used attributes, their default values and meaning
+
+|| Property|| Default value || Description ||
+| id | | (required) uniquely identifies the partition |
+| suffix | | (required) an LDAP DN ("dc=example, dc=com", for instance) |
+| cacheSize | -1 | cache size expressed as a number of entries |
+| optimizerEnabled | true | |
+| syncOnWrite | true | sync disks on every write operation |
+
+h4. Indexed Attributes
+
+The default partition implementation is based on JDBM. By default it may already index some common attributes like _objectClass_ and _ou_ for example. However you really want to index attributes that your applications use frequently in canned queries.
+
+Adding an index on an attribute is pretty simple. The configuration in the server.xml file needs to be altered before bulk loading data into the server. Otherwise your index will not work properly.
+
+{note}
+Indices must be configured before loading data into the server. Indices configured after loading entries into the server will NOT work properly unless they are built using the index builder command supplied with the ApacheDS tools command line program.
+{note}
+
+Indices are configured in the partition configuration section of your _server.xml_. Each partition will have it's own set of indexed attributes. These index configurations reside under the _indexedAttributes_ property of the _jdbmPartition_ element. Here's that section for the stock "dc=example,dc=com" partition that is configured out of the box with ApacheDS.
+
+{code:xml}
+...
+<jdbmPartition id="example" ...>
+ <indexedAttributes>
+ <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.1" cacheSize="100"/>
+ <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.2" cacheSize="100"/>
+ <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.3" cacheSize="100"/>
+ <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.4" cacheSize="100"/>
+ <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.5" cacheSize="10"/>
+ <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.6" cacheSize="10"/>
+ <jdbmIndex attributeId="1.3.6.1.4.1.18060.0.4.1.2.7" cacheSize="10"/>
+ <jdbmIndex attributeId="dc" cacheSize="100"/>
+ <jdbmIndex attributeId="ou" cacheSize="100"/>
+ <jdbmIndex attributeId="krb5PrincipalName" cacheSize="100"/>
+ <jdbmIndex attributeId="uid" cacheSize="100"/>
+ <jdbmIndex attributeId="objectClass" cacheSize="100"/>
+ </indexedAttributes>
+</jdbmPartition>
+...
+{code}
+
+As you can see indices are specified using a _jdbmIndex_ element. Just add one of these to your existing configuration setting the attributeId to the OID or name of the attribute you want to index. There is cacheSize parameter used to set the amount of cache on your index as well. Most of the time 100 will suffice no matter how big in capacity your server is.
+
+{quote}
+This number (100) is the number of entries stored in the cache, regardless to their size. Be carefull when dealing with huge entries - those which contains jpeg images or groups with many members.
+{quote}
+
+So if I wanted to index the attribute *initials* all I have to do is append the following xml fragment to this set of indexed attributes:
+{code:xml}
+...
+<jdbmPartition ...>
+ <indexedAttributes>
+ ...
+ <jdbmIndex attributeId="initials" cacheSize="100"/>
+ </indexedAttributes>
+ ...
+</jdbmPartition>
+...
+{code}
+
+That's it. Now queries on initials alone should perform about 50X faster.
+
+
+h4. Resources
+
+* Configuration Parameters Reference (to be done).
\ No newline at end of file
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/changing_the_admin_password.confluence
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/changing_the_admin_password.confluence?rev=1212094&view=auto
==============================================================================
--- directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/changing_the_admin_password.confluence (added)
+++ directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/changing_the_admin_password.confluence Thu Dec 8 20:33:52 2011
@@ -0,0 +1,46 @@
+h3. Changing the admin password
+
+This section describes the steps necessary to change the administrator password. Follow the instructions provided here step by step.
+
+{toc:type=list|minLevel=2|maxLevel=2}
+
+h4. Changing the password with Apache Directory Studio
+
+While the server is up and running, change the value of the _userPassword_ attribute of the admin (uid=admin,ou=system) via LDAP. There are several ways to accomplish this task. In the following, we use the Eclipse based Apache Directory Studio.
+
+A new LDAP connection with this tool is created via "New Connection ..." from the _Connections_ view. Enter your connection data in the first step ...
+
+!images/NewLDAPConnection1.png!
+
+... and in the next step, enter the admin DN _uid=admin,ou=system_ and the current password (default is "secret"). Saving the password is not necessary, we will change it anyway.
+
+!images/NewLDAPConnection2.png!
+
+Click _Finish_ to establish the connection.
+
+Afterwards, modify the value of the _userPassword_ attribute of the entry _uid=admin,ou=system_. Navigate to the entry in the DIT (_LDAP Browser_ view), and double click the attribute in the _Entry Editor_ view:
+
+!images/entryEditor.png!
+
+The Password Editor dialog shows up; enter the new password. You can optionally select a hash algorithm like _SHA_. In this case, the password will be stored one-way encrypted in the attribute value -- not a bad idea.
+
+!images/passwordEditor.png!
+
+Pressing _OK_ stores the new value, it is valid immediately. No need to restart the server, as it was in ApacheDS 1.0
+Close the connection in the _Connections_ view of Apache Directory Studio.
+
+h4. Verification
+
+Verify that you can login as admin with the new password. With Apache Directory Studio, you can change the properties of the existing connection profile via a right click in the _Connections_ view and a selection of the _Properties_ menu item. The following dialog appears:
+
+!images/connectionProperties.png!
+
+Enter the new password and press _OK_. Establishing a connection should now work.
+
+h4. Other ways to change the password
+
+Because the only step necessary to accomplish this task is changing a single attribute value, you may use any LDAP client which allows you to manipulate data. This includes both graphical and command line tools. Learn more about the option in chapter [2. Managing data within your directory].
+
+h4. Resources
+
+* [Apache Directory Studio|http://directory.apache.org/ldapstudio/|directory.apache.org]: The tool used here to perform the change
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/configure_logging.confluence
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/configure_logging.confluence?rev=1212094&view=auto
==============================================================================
--- directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/configure_logging.confluence (added)
+++ directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/basic_configuration_tasks/configure_logging.confluence Thu Dec 8 20:33:52 2011
@@ -0,0 +1,182 @@
+h3. Configure logging
+
+In order to detect and analyze problems, adjusting the log level of a server can be a valuable tool. This section describes how to configure logging within a standalone ApacheDS.
+
+{toc:type=list|minLevel=2|maxLevel=2}
+
+h4. ApacheDS and logging
+
+ApacheDS uses [SLF4J|http://www.slf4j.org/|www.slf4j.org] as its logging solution. This is a simple facade for various logging APIs. The default for ApacheDS 2.0 is [log4j|http://logging.apache.org/log4j/|logging.apache.org].
+
+h4. Default behavior after installation
+
+Without modification, the ApacheDS default instance writes log files in the directory _<APACHDS_HOME>/instances/default/log/_. Besides stdout, a [RollingFileAppender|http://logging.apache.org/log4j/docs/api/org/apache/log4j/RollingFileAppender.html|log4j javadoc] is used to collect warnings and errors. It backups the log files when they reach a certain size.
+
+Here is what the default configuration file _log4j.properties_ for the default instance, which is located in _<APACHDS_HOME>/instances/default/conf/_, looks like.
+The name of the _RollingFileAppender_ is "R":
+
+
+{code}
+log4j.rootCategory=WARN, R, stdout
+
+log4j.appender.stdout=org.apache.log4j.ConsoleAppender
+log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
+
+log4j.appender.R=org.apache.log4j.RollingFileAppender
+log4j.appender.R.File=${apacheds.log.dir}/apacheds-rolling.log
+
+log4j.appender.R.MaxFileSize=1024KB
+# Keep some backup files
+log4j.appender.R.MaxBackupIndex=5
+
+log4j.appender.R.layout=org.apache.log4j.PatternLayout
+log4j.appender.R.layout.ConversionPattern=[%d{HH:mm:ss}] %p [%c] - %m%n
+
+log4j.appender.stdout.layout.ConversionPattern=[%d{HH:mm:ss}] %p [%c] - %m%n
+
+# with these we'll not get innundated when switching to DEBUG
+log4j.logger.org.apache.directory.shared.ldap.name=WARN
+log4j.logger.org.springframework=WARN
+log4j.logger.org.apache.directory.shared.codec=WARN
+log4j.logger.org.apache.directory.shared.asn1=WARN
+{code}
+
+In this file, "R" is configured like this:
+
+|| Property name || Value in file above || Meaning ||
+| File | $\{apacheds.log.dir\}/apacheds-rolling.log | path to the output log file |
+| MaxFileSize | 1024KB | maximum size that the output file is allowed to reach before being rolled over to backup files |
+| MaxBackupIndex | 5 | number of backup files kept |
+| layout.ConversionPattern | \[%d\{HH:mm:ss\}\] %p \[%c\] - %m%n | format string for logging events |
+
+If the default logging does not meet your requirements, you can easily adjust the configuration to your needs.
+
+h4. Adjusting logging to your needs
+
+h5. Log file location (where the log files are placed)
+
+The location where the log files are placed can be changed.
+
+h6. Windows
+
+As you have noticed, the configuration for the log file within _log4j.properties_ uses a variable called $\{apacheds.log.dir\}. The variable is handed over to ApacheDS via the wrapper. This is configured in _<APACHDS_HOME>/conf/apacheds.conf_:
+
+{noformat}
+...
+# Java Additional Parameters
+wrapper.java.additional.1=-Dlog4j.configuration="file:///%INSTANCE_HOME%/%INSTANCE%/conf/log4j.properties"
+wrapper.java.additional.2=-Dapacheds.var.dir="%INSTANCE_HOME%/%INSTANCE%"
+wrapper.java.additional.3=-Dapacheds.log.dir="%INSTANCE_HOME%/%INSTANCE%/log"
+wrapper.java.additional.4=-Dapacheds.run.dir="%INSTANCE_HOME%/%INSTANCE%/run"
+wrapper.java.additional.5=-Dapacheds.instance=%INSTANCE%
+...
+{noformat}
+
+It is possible, to adjust the value here for all ApacheDS instances.
+
+For the _default_ instance (or any other instance), you may change the value within the file _<APACHDS_HOME>/instances/default/conf/apacheds.conf_ as well; it overrides the values of the general file.
+
+h6. Linux/MacOS/Solaris
+
+to be investigated, whether it is different than on Windows
+
+h5. Log level (how detailed the logs are)
+
+The following log levels from log4j are used for messages within ApacheDS:
+
+|| Level || Description from log4j documentation ||
+| DEBUG | designates fine-grained informational events that are most useful to debug an application |
+| INFO| designates informational messages that highlight the progress of the application at coarse-grained level |
+| WARN| designates potentially harmful situations |
+| ERROR| designates error events that might still allow the application to continue running |
+| FATAL | designates very severe error events that will presumably lead the application to abort |
+
+The default (global) log level in the configuration is _WARN_. All messages of level WARN and more severe (ERROR, FATAL) are written to the rolling log file. The easiest way to get finer log messages is to change it like this
+
+{code}
+log4j.rootCategory=DEBUG, stdout, R
+...
+{code}
+
+These detailed log messages took much file space and time and therefore should only be enabled globally in order to analyze problems.
+
+It is possible to configure the logging more fine grained by using categories. Within the default configuration there are some examples:
+
+{code}
+...
+# with these we'll not get innundated when switching to DEBUG
+log4j.logger.org.apache.directory.shared.ldap.name=WARN
+log4j.logger.org.springframework=WARN
+log4j.logger.org.apache.directory.shared.codec=WARN
+log4j.logger.org.apache.directory.shared.asn1=WARN
+{code}
+
+If the global level is switched to DEBUG, these definitions override the setting with WARN for certain areas and therefore keep the file a little bit smaller. Learn more about the concept of categories in the [Short introduction to log4j|http://logging.apache.org/log4j/docs/manual.html].
+
+h5. Format for log messages
+
+The format of each line within a log file is controlled by a pattern. For the _RollingFileAppender_ in the default configuration it looks like this
+
+{code}
+...
+log4j.appender.R.layout=org.apache.log4j.PatternLayout
+log4j.appender.R.layout.ConversionPattern=[%d{HH:mm:ss}] %p [%c] - %m%n
+...
+{code}
+
+Some examples lines within the log file, formatted with the pattern "\[%d\{HH:mm:ss\}\] %p \[%c\] - %m%n" are:
+
+{code}
+...
+[12:29:03] WARN [org.apache.directory.server.core.DefaultDirectoryService]
+ - You didn't change the admin password of directory service instance 'default'.
+ Please update the admin password as soon as possible to prevent a possible security breach.
+...
+[12:29:05] INFO [org.apache.directory.server.jndi.ServerContextFactory]
+ - Successful bind of an LDAP Service (636) is complete.
+[12:29:05] INFO [org.apache.directory.server.Service] - server: started in 6750 milliseconds
+...
+{code}
+
+The pattern uses the following conversion characters:
+
+|| Character || Outputs ||
+| %d | date of the logging event in the given format. like "12:29:05" for %d\{HH:mm:ss\} |
+| %p | priority (level) of the logging event, like "INFO" or "WARN" |
+| %c | category of the logging event, like "org.apache.directory.server.Service" |
+| %m | application supplied message associated with the logging event |
+| %n | platform dependent line separator |
+
+The [javadoc of log4j|http://logging.apache.org/log4j/docs/api/org/apache/log4j/PatternLayout.html|javadoc of log4j PatternLayout class] contains a table with all valid %-characters and their meaning.
+
+Simple adjust the pattern in the _log4j.properties file_ to get the log format of your choice, for instance
+
+{code}
+log4j.appender.R.layout.ConversionPattern=[%d{dd.MM.yyyy HH:mm:ss}] %p: %c{1}.%M() - %m%n
+{code}
+
+leads to messages of this form:
+
+{code}
+...
+[29.12.2006 13:50:44] INFO: ServerContextFactory.startLDAP0()
+ - Successful bind of an LDAP Service (636) is complete.
+[29.12.2006 13:50:44] INFO: Service.init() - server: started in 3016 milliseconds
+...
+{code}
+
+{warning:title=Warning}
+"Generating caller location information like with %M or %L is extremely slow. Its use should be avoided unless execution speed is not an issue." (from the log4j documentation)
+{warning}
+
+h5. Advanced log4j configuration
+
+You can take advantage of other features of log4j as well, such as other appenders like the daily rolling file appender. And you can configure logging to make it easier for you to view the messages with tools like Log Factor 5 or [Chainsaw|http://logging.apache.org/log4j/docs/chainsaw.html|logging.apache.org].
+
+Learn more about log4j and related tools at its [homepage|http://logging.apache.org/log4j/docs/index.html|log4j homepage].
+
+h4. Resources
+
+* [Short introduction to log4j|http://logging.apache.org/log4j/docs/manual.html|logging.apache.org]
+
+
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/installing_and_starting_the_server.confluence
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/installing_and_starting_the_server.confluence?rev=1212094&view=auto
==============================================================================
--- directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/installing_and_starting_the_server.confluence (added)
+++ directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/installing_and_starting_the_server.confluence Thu Dec 8 20:33:52 2011
@@ -0,0 +1 @@
+h2. Installing and starting the server
\ No newline at end of file
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/some_background_directories_directory_services_and_ldap.confluence
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/some_background_directories_directory_services_and_ldap.confluence?rev=1212094&view=auto
==============================================================================
--- directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/some_background_directories_directory_services_and_ldap.confluence (added)
+++ directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/some_background_directories_directory_services_and_ldap.confluence Thu Dec 8 20:33:52 2011
@@ -0,0 +1,90 @@
+h2. Some Background. Directories, directory services and LDAP
+
+This section provides a brief overview about directories, directory services and LDAP. Furthermore you find links to different resources (books, online resources, ...), which may act as introduction to the topic. If you are already an LDAP expert, you'll probably skip this section.
+
+{toc:type=list|minLevel=2|maxLevel=2}
+
+h3. Directories and directory services
+
+Generally speaking, a directory is a collection or list of data. Real world examples are telephone books (public or within organizations), church/land registers and listings of works (e.g. the Koechel-index, which lists all compositions of Mozart). All these examples have the purpose to preserve information and to make it available on demand to whom it may concern.
+
+Within information technology the term *directory* is used for a special kind of data storage. It allows the structured storage and efficient retrieval of objects which are often derived from the real world (e.g. persons, IT equipment). Characteristic:
+* all data is stored in so called *entries*
+* the set of entries within a directory forms a tree (hierarchical database)
+
+A *directory service* is a solution which offers users access to the information stored in the directory. A directory assistance (call center agent) is a good real world example for such a service. Within information technologies, such services are normally provided by software components. Directory services provide access to the content of a directory via a well-defined interface. If a network is used, an appropriate protocol has to be defined. LDAP (see below) is such a protocol.
+
+The real world examples mentioned above may be stored in such a directory, although other types of storage systems can be more appropriate (this depends on circumstance/requirements). At first sight directories compete thereby as data storage with the established relational data bases. However in the most large enterprises and organizations both directory services and relational databases are actually used. Read how Vikas Mahajan describes directories and databases as complementary, not competitive, solutions in his excellent article ["Should I Use a Directory, a Database, or Both?"|http://support.novell.com/techcenter/articles/ana20011101.html|support.novell.com].
+
+h3. LDAP -- the Lightweight Directory Access Protocol
+
+h4. What is it? Some history.
+
+The comprehensive standard *X.500*, finalized in 1988, builds the foundation for many of today's directory solutions. Within this standard, the client accesses the server via the Directory Access Protocol (*DAP*), which is OSI protocol stack based. With the Internet boom in the nineties, the accessibility of directories via TCP/IP became more and more important. Hence a TCP/IP-based access method, which in functionality was a subset of DAP, was standardized in 1993: the *Lightweight Directory Access Protocol (LDAP)*. First LDAP implementations were gateway solutions, they mediated between LDAP clients and X.500 servers. In 1995 the University of Michigan presented the first native LDAP server; in the meantime the work is continued by the [OpenLDAP|http://www.openldap.org/|www.openldap.org] project. 1996 Netscape followed with the first commercial LDAP server (Netscape Directory Server, foundation of several later LDAP servers). Other examples (among many others) include [Mi
crosoft Active Directory|http://www.microsoft.com/ad/|www.microsoft.com] and [Novell eDirectory|http://www.novell.com/products/edirectory/|www.novell.com]. The figure below shows the development of directory protocols from X.500/DAP to LDAP.
+
+!images/fromX500toLDAP.png!
+
+h4. Information model primer
+
+Within the information model of LDAP, data is stored in entries, which build up a hierarchical, tree like structure. Each entry has a unique name (*DN*, *Distinguished Name*), which depicts its position within the tree. An entry consists of key/value pairs, the *attributes*. Some attributes may occur more than once within an entry (single or multi valued, e.g. a person can have more than one telephone number). So called *object classes* define, which attributes an entry may have, and which of them are required. The classes build up a hierarchy with *top* as root; there is a parallelism to the object oriented world. top forces only the attribute objectclass, which assigns an entry its object classes. A *schema* consists object classes and attribute types, and therefore defines, what kind of entries can be stored within the directory. Directory servers ship a schema out-of-the-box, often with elements standardized by RFCs. In addition, most directory solutions allow you to def
ine custom object classes and attributes. But in practice, the pre-defined elements are used. Sometimes they get extended according to special requirements.
+
+h4. Common applications of LDAP based directories
+
+LDAP operations include entry creation, modification, deletion and search. As a general rule, LDAP directories are optimized for read and search operations, at the cost of write performance. Data, which will be modified often, therefore better suits in a relational database, which offers better support for transactions and referential integrity as well. Directories are rather used if comparatively stable data has to be provided centrally.
+Common examples are network resources (printers, services) and user data (including credentials and rights for the resources). As a notable feature, many directory products offer replicas, which permit better access times and higher availability especially in geographically dispersed organizations. Not for nothing, the most common LDAP application is the enterprise phone book. That even Microsoft Outlook may be an LDAP client in this case - most average users probably don't know.
+
+
+h4. Examples of software components which support LDAP
+
+!images/ldap-tools.png!
+
+Very different types of software products may act as LDAP clients, consuming data for authentication, authorization or data presentation etc.
+
+* E-Mail clients (e.g. Mozilla Thunderbird)
+* LDAP tools (e.g. Apache Directory Studio)
+* Web servers (e.g. Apache Tomcat, Apache HTTP Server)
+* Mail servers (e.g. Apache James)
+* ...
+
+Configuration details for several of these programs in conjunction with ApacheDS are described in later sections.
+
+h3. LDAP resources
+
+h4. Books
+
+There are several good LDAP books available. Here are two examples which provide sample chapters on their homepages.
+
+h5. Understanding and Deploying LDAP Directory Services
+
+!images/cover_howes_100.gif!
+
+Understanding and Deploying LDAP Directory Services (2nd Edition)
+by Timothy A. Howes, Mark C. Smith, Gordon S. Good, Tim Howes
+Addison-Wesley Professional, 2nd Edition 2003
+ISBN: 0-672323-16-8
+
+[Book's Homepage (Howes)|http://awprofessional.com/title/0672323168]
+
+h5. LDAP fuer Java-Entwickler
+
+!images/cover_zoerner_100.gif!
+
+LDAP fuer Java-Entwickler -- Einstieg und Integration. !images/de.png!
+von Stefan Zoerner
+Software und Support Verlag, 3. aktualisierte Auflage 2007
+ISBN: 978-3-939084-07-5
+
+[Webseite zum Buch (Zoerner)|http://www.entwickler-press.de/|www.entwickler-press.de]
+
+h4. Articles, forums, blogs and other online resources
+
+h5. Blogs
+
+* [cn=Directory Manager - All about Directory Server|http://blogs.sun.com/roller/page/DirectoryManager|blogs.sun.com], Sun Blog
+
+h5. Articles and other online resources
+
+* [Understanding LDAP - Design and Implementation|http://www.redbooks.ibm.com/abstracts/SG244986.html?Open|www.redbooks.ibm.com], IBM RedBook, July 2006
+* [Demystifying LDAP |http://www.oreillynet.com/pub/a/sysadmin/2006/07/27/demystifying-ldap.html|www.oreillynet.com] by Brian K. Jones, O'Reilly Network
+* [LDAP verstehen mit linx|http://www.mitlinx.de/ldap/|www.mitlinx.de], by Petra Haberer !images/de.png!
+
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/what-apache-directory-server-is.confluence
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/what-apache-directory-server-is.confluence?rev=1212094&view=auto
==============================================================================
--- directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/what-apache-directory-server-is.confluence (added)
+++ directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/how-to-begin/what-apache-directory-server-is.confluence Thu Dec 8 20:33:52 2011
@@ -0,0 +1,36 @@
+h2. What Apache Directory Server is
+
+This section describes what Apache Directory Server (abbreviated ApacheDS) is, and where it comes from.
+
+{toc:type=list|minLevel=2|maxLevel=2}
+
+h3. System vision
+
+ApacheDS 2.0 is an embeddable, extendable, standards compliant, modern LDAP server written entirely in Java, and available under the Apache Software License. Other network protocols like Kerberos and NTP are supported as well (and even more may be added), but basically (and especially for this introduction guide) ApacheDS is an LDAP server.
+
+_Embeddable_ means that it is possible to configure, start and stop ApacheDS from other Java components, especially application servers, and the server runs within the same VM. The solution has already been successfully embedded in Apache Geronimo, JBoss, and others. The fact that the server is embeddable is quite interesting, nevertheless you also have the deployment option to run the server standalone, for instance as a Windows service. Perhaps you know this situation from other LDAP servers -- open source (like OpenLDAP) as well as commercial ones (like Sun Java System Directory Server). This guide is dedicated to people that are new to ApacheDS. The guide concentrates on installing, configuring and running ApacheDS in a standalone configuration.
+
+_Extendable_ means that the modern architecture of the solution provides many extension points. Write your own partitions to store directory data, interceptors to add functionality, etc. by implementing certain interfaces and plugging them in using Spring.
+
+_Standard compliant_ means that ApacheDS 2.0 adheres to all RFCs relevant to LDAPv3. Please note that version 1.0 of the server has been successfully certified by the Open Group in September 2006 ("LDAP certified"). Thus LDAP clients may rightly expect that ApacheDS behaves like they expect.
+
+_Modern_ means that ApacheDS aims modernize the LDAP territory, as well as it favors standards compliance. New rich integration tier constructs like LDAP Stored Procedures and Triggers are being built on top of existing standards.
+
+_Entirely written in Java_ means that the software compiles and runs on a huge number of hardware and software platforms. Native installers are available for Windows, MacOS and Solaris (both SPARC and intel platform), but in fact the set of possible targets is by far more extensive.
+
+h4. Architectural overview
+
+!images/50k-ft-architecture.png!
+
+h3. Origin and Motives
+
+Through his experiences with enterprise LDAP directories, Alex Karasulu, realized there is a great need for rich integration tier constructs like LDAP Stored Procedures, Triggers, and Views. In 2001 he set out to alter the OpenLDAP server to offer support for these useful facilities which are present in relational databases but missing in the LDAP world. Alex's attempts failed due to the complexity of the software which was brittle, and difficult to manage. As C code ported to several platforms, the OpenLDAP code base, had several #IFDEF conditional pre-compiler directives that made it difficult to change the code. At this point Alex thought about implementing a new LDAP server in pure Java. Thanks to NIO this was finally possible using the 1.4 JDK.
+
+In October 2002 Alex Karasulu founded and registered the [LDAPd|http://sourceforge.net/projects/ldapd] project at SourceForge.net. LDAPd was a a pure Java embeddable LDAP v3 protocol daemon built on the Avalon framework. Alex donated the code to the Apache Software Foundation and the code entered the [Apache Incubator|http://incubator.apache.org/|Apache Incubator Homepage] in October 2003. One year later in October of 2004, the Apache Directory Top Level Project (TLP) was formed after a successful incubation with the now called Apache Directory Server as its flagship product. After 4 years of development, in October 2006, Apache Directory Server 1.0 was released as an Open Group certified LDAPv3 protocol server. The certification has been renewed in September 2007.
+
+Having a standards compliant and modern LDAP server, Apache Directory Team is now working on Identity and Access Management solutions leveraging the directory technology.
+
+h3. Resources
+
+* [Proposal for an Apache Directory Project|http://directory.apache.org/community%26resources/proposal-for-an-apache-directory-project.html|directory.apache.org] the original proposal for incubation, September 2003.
+* [Architecting the Modern LDAP Renaissance: The Apache Directory Vision|http://directory.apache.org/community%26resources/ldap-renaissance.html|directory.apache.org], Paper for 1st International Conference on LDAP, September 2007.
\ No newline at end of file
Modified: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/NewLDAPConnection1.png
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/NewLDAPConnection1.png?rev=1212094&r1=1212093&r2=1212094&view=diff
==============================================================================
Binary files - no diff available.
Modified: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/NewLDAPConnection2.png
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/NewLDAPConnection2.png?rev=1212094&r1=1212093&r2=1212094&view=diff
==============================================================================
Binary files - no diff available.
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/apache_directory_studio.png
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/apache_directory_studio.png?rev=1212094&view=auto
==============================================================================
Binary file - no diff available.
Propchange: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/apache_directory_studio.png
------------------------------------------------------------------------------
svn:mime-type = image/png
Modified: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/connectionProperties.png
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/connectionProperties.png?rev=1212094&r1=1212093&r2=1212094&view=diff
==============================================================================
Binary files - no diff available.
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/copy-entry-subtree-depth-in-directory-studio.PNG.jpg
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/copy-entry-subtree-depth-in-directory-studio.PNG.jpg?rev=1212094&view=auto
==============================================================================
Binary file - no diff available.
Propchange: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/copy-entry-subtree-depth-in-directory-studio.PNG.jpg
------------------------------------------------------------------------------
svn:mime-type = image/jpeg
Modified: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/entryEditor.png
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/entryEditor.png?rev=1212094&r1=1212093&r2=1212094&view=diff
==============================================================================
Binary files - no diff available.
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/partitionsuffix-sevenseas-in-directory-studio.PNG.jpg
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/partitionsuffix-sevenseas-in-directory-studio.PNG.jpg?rev=1212094&view=auto
==============================================================================
Binary file - no diff available.
Propchange: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/partitionsuffix-sevenseas-in-directory-studio.PNG.jpg
------------------------------------------------------------------------------
svn:mime-type = image/jpeg
Modified: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/passwordEditor.png
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/passwordEditor.png?rev=1212094&r1=1212093&r2=1212094&view=diff
==============================================================================
Binary files - no diff available.
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/properties_root_dse.png.jpg
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/properties_root_dse.png.jpg?rev=1212094&view=auto
==============================================================================
Binary file - no diff available.
Propchange: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/properties_root_dse.png.jpg
------------------------------------------------------------------------------
svn:mime-type = image/jpeg
Added: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/sample_data_bug_structure.png
URL: http://svn.apache.org/viewvc/directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/sample_data_bug_structure.png?rev=1212094&view=auto
==============================================================================
Binary file - no diff available.
Propchange: directory/documentation/apacheds-manuals/trunk/src/basic-user-guide-confluence/images/sample_data_bug_structure.png
------------------------------------------------------------------------------
svn:mime-type = image/png