directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From elecha...@apache.org
Subject svn commit: r1403441 - in /directory/site/trunk/content/apacheds/basic-ug: ./ images/
Date Mon, 29 Oct 2012 17:34:37 GMT
Author: elecharny
Date: Mon Oct 29 17:34:36 2012
New Revision: 1403441

URL: http://svn.apache.org/viewvc?rev=1403441&view=rev
Log:
Added a missing image, fixed all the pages links

Added:
    directory/site/trunk/content/apacheds/basic-ug/images/w32_service_properties.png   (with props)
Modified:
    directory/site/trunk/content/apacheds/basic-ug/1-how-to-begin.mdtext
    directory/site/trunk/content/apacheds/basic-ug/1.4.1-changing-server-port.mdtext
    directory/site/trunk/content/apacheds/basic-ug/1.4.4-configure-logging.mdtext
    directory/site/trunk/content/apacheds/basic-ug/1.4.5-anonymous-access.mdtext
    directory/site/trunk/content/apacheds/basic-ug/1.5-sample-configuration.mdtext
    directory/site/trunk/content/apacheds/basic-ug/3-basic-security.mdtext
    directory/site/trunk/content/apacheds/basic-ug/3.1-authentication-options.mdtext
    directory/site/trunk/content/apacheds/basic-ug/3.2-basic-authorization.mdtext
    directory/site/trunk/content/apacheds/basic-ug/3.3-enabling-ssl.mdtext
    directory/site/trunk/content/apacheds/basic-ug/4-integrating-apacheds.mdtext
    directory/site/trunk/content/apacheds/basic-ug/4.1-mozilla-thunderbird.mdtext

Modified: directory/site/trunk/content/apacheds/basic-ug/1-how-to-begin.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/1-how-to-begin.mdtext?rev=1403441&r1=1403440&r2=1403441&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/basic-ug/1-how-to-begin.mdtext (original)
+++ directory/site/trunk/content/apacheds/basic-ug/1-how-to-begin.mdtext Mon Oct 29 17:34:36 2012
@@ -1,7 +1,7 @@
 Title: 1 - How To Begin
 NavUp: ../basic-users-guide.html
 NavUpText: Basic User Guide
-NavNext: ../2-handling-data.html
+NavNext: 2-handling-data.html
 NavNextText: Chapter 2 - Handing Data
 Notice: Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file

Modified: directory/site/trunk/content/apacheds/basic-ug/1.4.1-changing-server-port.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/1.4.1-changing-server-port.mdtext?rev=1403441&r1=1403440&r2=1403441&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/basic-ug/1.4.1-changing-server-port.mdtext (original)
+++ directory/site/trunk/content/apacheds/basic-ug/1.4.1-changing-server-port.mdtext Mon Oct 29 17:34:36 2012
@@ -1,4 +1,6 @@
 Title: 1.4.1 - Changing the server port for LDAP
+NavPrev: 1.4-basic-configuration-tasks.html
+NavPrevText: 1.4 - Basic configuration tasks
 NavUp: 1.4-basic-configuration-tasks.html
 NavUpText: 1.4 - Basic configuration tasks
 NavNext: 1.4.2-changing-admin-password.html

Modified: directory/site/trunk/content/apacheds/basic-ug/1.4.4-configure-logging.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/1.4.4-configure-logging.mdtext?rev=1403441&r1=1403440&r2=1403441&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/basic-ug/1.4.4-configure-logging.mdtext (original)
+++ directory/site/trunk/content/apacheds/basic-ug/1.4.4-configure-logging.mdtext Mon Oct 29 17:34:36 2012
@@ -24,4 +24,253 @@ Notice: Licensed to the Apache Software 
 
 # 1.4.4 - Configure logging
 
-TODO
\ No newline at end of file
+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]
+
+## ApacheDS and logging 
+
+ApacheDS 2.0 uses [SLF4J](http://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/).
+
+## Default behavior after installation
+
+By default, ApacheDS writes log files in the directory _<APACHDS_HOME>/var/log/_. Besides stdout, a [RollingFileAppender](http://logging.apache.org/log4j/docs/api/org/apache/log4j/RollingFileAppender.html) 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_, which is located in _<APACHDS_HOME>/conf/_, looks like.
+The name of the _RollingFileAppender_ is "R":
+
+	log4j.rootCategory=WARN, stdout, R
+	
+	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-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
+
+In this file "R" is configured like this:
+
+<div class="table-wrap">
+	<table class="confluenceTable">
+		<tbody>
+			<tr>
+				<th class="confluenceTh"> Property name </th>
+				<th class="confluenceTh"> Value in file above </th>
+				<th class="confluenceTh"> Meaning </th>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> File </td>
+				<td class="confluenceTd"> apacheds-rolling.log </td>
+				<td class="confluenceTd"> path to the output log file, in our case relative to <em>var/log</em> </td>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> MaxFileSize </td>
+				<td class="confluenceTd"> 1024KB </td>
+				<td class="confluenceTd"> maximum size that the output file is allowed to reach before being rolled over to backup files </td>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> MaxBackupIndex </td>
+				<td class="confluenceTd"> 5 </td>
+				<td class="confluenceTd"> number of backup files kept </td>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> layout.ConversionPattern </td>
+				<td class="confluenceTd"> [%d{HH:mm:ss}] %p [%c] - %m%n </td>
+				<td class="confluenceTd"> format string for logging events </td>
+			</tr>
+		</tbody>
+	</table>
+</div>
+
+If the default logging does not meet your requirements, you can easily adjust the configuration to your needs.
+
+## Adjusting logging to your needs
+
+### Log file location (where the log files are placed)
+
+By default the log files are placed at _<APACHDS_HOME>/var/log/_, but that can be changed.
+
+#### Linux/MacOS/Solaris
+On this systems the location of the log files is configured via an entry in */bin/server.init*. Look for the following lines and change it to your preferences:
+
+	$DAEMON_HOME/apacheds \
+	...
+	-outfile $SERVER_HOME/var/log/apacheds-stdout.log \
+	-errfile $SERVER_HOME/var/log/apacheds-stderr.log \
+	...    
+	$APACHEDS_HOME start
+
+#### Windows
+
+On Windows you can use the configuration wizard for the service as shown in the screenshot above. To adjust the log path you have to adjust the values of *Redirect Stdout* and *Redirect Stderror*
+
+### Log level (how detailed the logs are)
+
+The following log levels from log4j are used for messages within ApacheDS:
+
+<div class="table-wrap">
+	<table class="confluenceTable">
+		<tbody>
+			<tr>
+				<th class="confluenceTh"> Level </th>
+				<th class="confluenceTh"> Description from log4j documentation </th>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> DEBUG </td>
+				<td class="confluenceTd"> designates fine-grained informational events that are most useful to debug an application </td>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> INFO</td>
+				<td class="confluenceTd"> designates informational messages that highlight the progress of the application at coarse-grained level </td>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> WARN</td>
+				<td class="confluenceTd"> designates potentially harmful situations </td>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> ERROR</td>
+				<td class="confluenceTd"> designates error events that might still allow the application to continue running </td>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> FATAL </td>
+				<td class="confluenceTd"> designates very severe error events that will presumably lead the application to abort </td>
+			</tr>
+		</tbody>
+	</table>
+</div>
+
+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
+
+	log4j.rootCategory=DEBUG, stdout, R
+	...
+
+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:
+
+	...
+	# 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
+
+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). 
+
+### 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
+
+	...
+	log4j.appender.R.layout=org.apache.log4j.PatternLayout
+	log4j.appender.R.layout.ConversionPattern=[%d{HH:mm:ss}] %p [%c] - %m%n
+	...
+
+Some examples lines within the log file, formatted with the pattern "\[%d\{HH:mm:ss\}\] %p \[%c\] - %m%n" are:
+
+	...
+	[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
+	...
+
+The pattern uses the following conversion characters:
+
+<div class="table-wrap">
+	<table class="confluenceTable">
+		<tbody>
+			<tr>
+				<th class="confluenceTh"> Character </th>
+				<th class="confluenceTh"> Outputs </th>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> %d </td>
+				<td class="confluenceTd"> date of the logging event in the given format. like "12:29:05" for %d{HH:mm:ss}  </td>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> %p </td>
+				<td class="confluenceTd"> priority (level) of the logging event, like "INFO" or "WARN" </td>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> %c </td>
+				<td class="confluenceTd"> category of the logging event, like "org.apache.directory.server.Service" </td>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> %m </td>
+				<td class="confluenceTd"> application supplied message associated with the logging event </td>
+			</tr>
+			<tr>
+				<td class="confluenceTd"> %n </td>
+				<td class="confluenceTd"> platform dependent line separator </td>
+			</tr>
+		</tbody>
+	</table>
+</div>
+
+The [javadoc of log4j](http://logging.apache.org/log4j/docs/api/org/apache/log4j/PatternLayout.html) 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
+
+	log4j.appender.R.layout.ConversionPattern=[%d{dd.MM.yyyy HH:mm:ss}] %p: %c{1}.%M() - %m%n
+
+leads to messages of this form:
+
+	...
+	[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
+	...
+
+<DIV class="warning" markdown="1">
+** 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)
+</DIV>
+
+### 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).
+
+Learn more about log4j and related tools at its [homepage](http://logging.apache.org/log4j/docs/index.html).
+
+## Example configurations
+
+The following example could be used to log all incoming search, add, delete, modify and moddn requests:
+
+	log4j.logger.org.apache.directory.server.ldap.handlers.SearchHandler=DEBUG
+	log4j.logger.org.apache.directory.server.ldap.handlers.AddHandler=DEBUG
+	log4j.logger.org.apache.directory.server.ldap.handlers.DeleteHandler=DEBUG
+	log4j.logger.org.apache.directory.server.ldap.handlers.ModifyHandler=DEBUG
+	log4j.logger.org.apache.directory.server.ldap.handlers.ModifyDnHandler=DEBUG
+
+## Log settings of the Windows daemon process 
+
+After installation on Windows, you have the option to configure the ApacheDS Windows Service (you can do this later as well). If you do so, one option pane is dedicated to logging:
+
+![Windows service properties](images/w32_service_properties.png)
+
+You can adjust the logging level and a log path. Note that this is for the daemon only. The server itself is configured as described above.
+
+## Resources
+
+* [Short introduction to log4j](http://logging.apache.org/log4j/docs/manual.html)
+
+

Modified: directory/site/trunk/content/apacheds/basic-ug/1.4.5-anonymous-access.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/1.4.5-anonymous-access.mdtext?rev=1403441&r1=1403440&r2=1403441&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/basic-ug/1.4.5-anonymous-access.mdtext (original)
+++ directory/site/trunk/content/apacheds/basic-ug/1.4.5-anonymous-access.mdtext Mon Oct 29 17:34:36 2012
@@ -3,6 +3,8 @@ NavPrev: 1.4.4-configure-logging.html
 NavprevText: 1.4.4 - Configure logging
 NavUp: 1.4-basic-configuration-tasks.html
 NavUpText: 1.4 - Basic configuration tasks
+NavNext: 1.5-about-sample-configuration.html
+NavNextText: 1.5. - About the sample configurations and sample directory data	
 Notice: Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
     distributed with this work for additional information

Modified: directory/site/trunk/content/apacheds/basic-ug/1.5-sample-configuration.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/1.5-sample-configuration.mdtext?rev=1403441&r1=1403440&r2=1403441&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/basic-ug/1.5-sample-configuration.mdtext (original)
+++ directory/site/trunk/content/apacheds/basic-ug/1.5-sample-configuration.mdtext Mon Oct 29 17:34:36 2012
@@ -1,8 +1,10 @@
-Title: 1.4.1 - Changing the server port for LDAP
-NavUp: 1.4-basic-configuration-tasks.html
-NavUpText: 1.4 - Basic configuration tasks
-NavNext: 1.4.2-changing-admin-password.html
-NavNextText: 1.4.2 - Changing the admin password
+Title: 1.5. - About the sample configurations and sample directory data	
+NavPrev: 1.4-basic-configuration-tasks.html
+NavprevText: 1.4 - Basic configuration tasks
+NavUp: 1-how-to-begin.html
+NavUpText: 1 - How to begin
+NavNext: 2-handling-data.html
+NavNextText: 2 - Handling of data within your directory
 Notice: Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
     distributed with this work for additional information
@@ -20,112 +22,4 @@ Notice: Licensed to the Apache Software 
     specific language governing permissions and limitations
     under the License.
 
-# 1.4.1 - Changing the server port for LDAP
-
-This section describes how to change to port for the LDAP protocol. There are two ways to do that : either you use the configuration plugin available in **Apache Directory Studio**, or you update the LDIF partition that contains the configuration.
-
-[TOC]
-
-## The task and how to accomplish it
-
-By default the LDAP server listens on port 10389 (unencrypted or StartTLS) and 10636 (SSL). It is quite common to run LDAP on 389, which is the well-known port for this protocol, but that requires the server to be started with a root user (or with sudo). Of course other options are imaginable as well. Changing the LDAP port is a good example for adjusting the existing Spring configuration as introduced in the last section.
-
-<DIV class="note" markdown="1">
-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.
-</DIV>
-
-
-Basically, there are two cases :
-* The server is not started
-* The server is started
-
-We will see how to change the port in those two cases.
-
-### Using Apache Directory Studio
-
-#### The server is started
-
-The best solution is to connect on the server using Studio, and to open it's configuration :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config1.png)
-</CENTER>
-
-When you select this menu, you will get the main configuration screen, containing the port for LDAP and LDAPS :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-
-Now, change the values of _port_ to your needs, then save the configuration. You have to restart the server afterwards in order to take this change into effect.
-
-#### The server is not started
-
-You can start it and update the configuration, of course. But if you want to configure the server when it's stopped, you will have to load the configuration file, which is on _.../instances/default/conf/config.ldif_, when the server has been installed using the default setting.
-
-Opening this file will open the exact same window :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-You can update the _ports_ and save the file.
-
-<DIV class="warning" markdown="1">
-	Note that you will requite write access on this file !
-</DIV>
-
-### Modifying the configuration LDIF partition
-
-All the **ApacheDS** configuration is stored as a LDIF file, and can be modified either using a text editor (although we don't consider this as a safe practice) or using a Modify request on a running server. 
-
-<DIV class="info" markdown="1">
-	Modifying the configuration on a running server will **not** change the listening port of the running server. You will have to relaunch the server in order to get this new configuration to be available.
-</DIV>
-
-
-The configuration is stored as a set of LDAP entries, so you can update one of them. In order to modify the entry containing the ports, you have first to find it, and second to send a valid modify request.
-
-All the **ApacheDS** configuration is stored under the _ou=config_ partition. The ports are stored in some entries under _DN: ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ads-directoryServiceId=default,ou=config_ (obviously, dependning on your installation, this DN might change : the _ads-directoryServiceId_ may have a different name, so is the _ads-serverId_). In any case, the _ou=transports_ branch contains two entries :
-
-for LDAP :
-
-	dn: ads-transportid=ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ad
-	 s-directoryServiceId=default,ou=config
-	ads-systemport: 10389
-	ads-enabled: TRUE
-	ads-transportnbthreads: 8
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldap
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	 
-and for LDAPS :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,a
-	 ds-directoryServiceId=default,ou=config
-	ads-systemport: 10636
-	ads-transportenablessl: TRUE
-	ads-enabled: TRUE
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldaps
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	
-You just have to send a ModifyRequest using such a LDIF :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,ads
-	 -directoryServiceId=default,ou=config
-	changetype: modify
-	replace: ads-systemport
-	ads-systemport: 10637
-	-
-
-(here, we have modified the LDAPS Port from 10636 to 10637)
-
-Those modification can be done directly on the _config.ldif_ file, but you won't have any syntax check if you do so.
\ No newline at end of file
+# 1.5. - About the sample configurations and sample directory data	
\ No newline at end of file

Modified: directory/site/trunk/content/apacheds/basic-ug/3-basic-security.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/3-basic-security.mdtext?rev=1403441&r1=1403440&r2=1403441&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/basic-ug/3-basic-security.mdtext (original)
+++ directory/site/trunk/content/apacheds/basic-ug/3-basic-security.mdtext Mon Oct 29 17:34:36 2012
@@ -1,8 +1,10 @@
-Title: 1.4.1 - Changing the server port for LDAP
-NavUp: 1.4-basic-configuration-tasks.html
-NavUpText: 1.4 - Basic configuration tasks
-NavNext: 1.4.2-changing-admin-password.html
-NavNextText: 1.4.2 - Changing the admin password
+Title: 3 - Basic Security
+NavPrev: 2-handling-data.html
+NavPrevtext: 2 - Handling of data within your directory
+NavUp: ../basic-users-guide.html
+NavUpText: Basic User Guide
+NavNext: 4-integrating-apacheds.html
+NavNextText: 4 - Integrating ApacheDS with other programs
 Notice: Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
     distributed with this work for additional information
@@ -20,112 +22,4 @@ Notice: Licensed to the Apache Software 
     specific language governing permissions and limitations
     under the License.
 
-# 1.4.1 - Changing the server port for LDAP
-
-This section describes how to change to port for the LDAP protocol. There are two ways to do that : either you use the configuration plugin available in **Apache Directory Studio**, or you update the LDIF partition that contains the configuration.
-
-[TOC]
-
-## The task and how to accomplish it
-
-By default the LDAP server listens on port 10389 (unencrypted or StartTLS) and 10636 (SSL). It is quite common to run LDAP on 389, which is the well-known port for this protocol, but that requires the server to be started with a root user (or with sudo). Of course other options are imaginable as well. Changing the LDAP port is a good example for adjusting the existing Spring configuration as introduced in the last section.
-
-<DIV class="note" markdown="1">
-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.
-</DIV>
-
-
-Basically, there are two cases :
-* The server is not started
-* The server is started
-
-We will see how to change the port in those two cases.
-
-### Using Apache Directory Studio
-
-#### The server is started
-
-The best solution is to connect on the server using Studio, and to open it's configuration :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config1.png)
-</CENTER>
-
-When you select this menu, you will get the main configuration screen, containing the port for LDAP and LDAPS :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-
-Now, change the values of _port_ to your needs, then save the configuration. You have to restart the server afterwards in order to take this change into effect.
-
-#### The server is not started
-
-You can start it and update the configuration, of course. But if you want to configure the server when it's stopped, you will have to load the configuration file, which is on _.../instances/default/conf/config.ldif_, when the server has been installed using the default setting.
-
-Opening this file will open the exact same window :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-You can update the _ports_ and save the file.
-
-<DIV class="warning" markdown="1">
-	Note that you will requite write access on this file !
-</DIV>
-
-### Modifying the configuration LDIF partition
-
-All the **ApacheDS** configuration is stored as a LDIF file, and can be modified either using a text editor (although we don't consider this as a safe practice) or using a Modify request on a running server. 
-
-<DIV class="info" markdown="1">
-	Modifying the configuration on a running server will **not** change the listening port of the running server. You will have to relaunch the server in order to get this new configuration to be available.
-</DIV>
-
-
-The configuration is stored as a set of LDAP entries, so you can update one of them. In order to modify the entry containing the ports, you have first to find it, and second to send a valid modify request.
-
-All the **ApacheDS** configuration is stored under the _ou=config_ partition. The ports are stored in some entries under _DN: ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ads-directoryServiceId=default,ou=config_ (obviously, dependning on your installation, this DN might change : the _ads-directoryServiceId_ may have a different name, so is the _ads-serverId_). In any case, the _ou=transports_ branch contains two entries :
-
-for LDAP :
-
-	dn: ads-transportid=ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ad
-	 s-directoryServiceId=default,ou=config
-	ads-systemport: 10389
-	ads-enabled: TRUE
-	ads-transportnbthreads: 8
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldap
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	 
-and for LDAPS :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,a
-	 ds-directoryServiceId=default,ou=config
-	ads-systemport: 10636
-	ads-transportenablessl: TRUE
-	ads-enabled: TRUE
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldaps
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	
-You just have to send a ModifyRequest using such a LDIF :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,ads
-	 -directoryServiceId=default,ou=config
-	changetype: modify
-	replace: ads-systemport
-	ads-systemport: 10637
-	-
-
-(here, we have modified the LDAPS Port from 10636 to 10637)
-
-Those modification can be done directly on the _config.ldif_ file, but you won't have any syntax check if you do so.
\ No newline at end of file
+# 3 - Basic Security
\ No newline at end of file

Modified: directory/site/trunk/content/apacheds/basic-ug/3.1-authentication-options.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/3.1-authentication-options.mdtext?rev=1403441&r1=1403440&r2=1403441&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/basic-ug/3.1-authentication-options.mdtext (original)
+++ directory/site/trunk/content/apacheds/basic-ug/3.1-authentication-options.mdtext Mon Oct 29 17:34:36 2012
@@ -1,8 +1,10 @@
-Title: 1.4.1 - Changing the server port for LDAP
-NavUp: 1.4-basic-configuration-tasks.html
-NavUpText: 1.4 - Basic configuration tasks
-NavNext: 1.4.2-changing-admin-password.html
-NavNextText: 1.4.2 - Changing the admin password
+Title: 3.1 - Authentication options
+Navprev: 3-basic-security.html
+NavPrevText: 3 - Basic Security
+NavUp: 3-basic-security.html
+NavUpText: 3 - Basic Security
+NavNext: 3.2-basic-authorization.html
+NavNextText: 3.2 - Basic authorization
 Notice: Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
     distributed with this work for additional information
@@ -20,112 +22,4 @@ Notice: Licensed to the Apache Software 
     specific language governing permissions and limitations
     under the License.
 
-# 1.4.1 - Changing the server port for LDAP
-
-This section describes how to change to port for the LDAP protocol. There are two ways to do that : either you use the configuration plugin available in **Apache Directory Studio**, or you update the LDIF partition that contains the configuration.
-
-[TOC]
-
-## The task and how to accomplish it
-
-By default the LDAP server listens on port 10389 (unencrypted or StartTLS) and 10636 (SSL). It is quite common to run LDAP on 389, which is the well-known port for this protocol, but that requires the server to be started with a root user (or with sudo). Of course other options are imaginable as well. Changing the LDAP port is a good example for adjusting the existing Spring configuration as introduced in the last section.
-
-<DIV class="note" markdown="1">
-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.
-</DIV>
-
-
-Basically, there are two cases :
-* The server is not started
-* The server is started
-
-We will see how to change the port in those two cases.
-
-### Using Apache Directory Studio
-
-#### The server is started
-
-The best solution is to connect on the server using Studio, and to open it's configuration :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config1.png)
-</CENTER>
-
-When you select this menu, you will get the main configuration screen, containing the port for LDAP and LDAPS :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-
-Now, change the values of _port_ to your needs, then save the configuration. You have to restart the server afterwards in order to take this change into effect.
-
-#### The server is not started
-
-You can start it and update the configuration, of course. But if you want to configure the server when it's stopped, you will have to load the configuration file, which is on _.../instances/default/conf/config.ldif_, when the server has been installed using the default setting.
-
-Opening this file will open the exact same window :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-You can update the _ports_ and save the file.
-
-<DIV class="warning" markdown="1">
-	Note that you will requite write access on this file !
-</DIV>
-
-### Modifying the configuration LDIF partition
-
-All the **ApacheDS** configuration is stored as a LDIF file, and can be modified either using a text editor (although we don't consider this as a safe practice) or using a Modify request on a running server. 
-
-<DIV class="info" markdown="1">
-	Modifying the configuration on a running server will **not** change the listening port of the running server. You will have to relaunch the server in order to get this new configuration to be available.
-</DIV>
-
-
-The configuration is stored as a set of LDAP entries, so you can update one of them. In order to modify the entry containing the ports, you have first to find it, and second to send a valid modify request.
-
-All the **ApacheDS** configuration is stored under the _ou=config_ partition. The ports are stored in some entries under _DN: ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ads-directoryServiceId=default,ou=config_ (obviously, dependning on your installation, this DN might change : the _ads-directoryServiceId_ may have a different name, so is the _ads-serverId_). In any case, the _ou=transports_ branch contains two entries :
-
-for LDAP :
-
-	dn: ads-transportid=ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ad
-	 s-directoryServiceId=default,ou=config
-	ads-systemport: 10389
-	ads-enabled: TRUE
-	ads-transportnbthreads: 8
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldap
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	 
-and for LDAPS :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,a
-	 ds-directoryServiceId=default,ou=config
-	ads-systemport: 10636
-	ads-transportenablessl: TRUE
-	ads-enabled: TRUE
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldaps
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	
-You just have to send a ModifyRequest using such a LDIF :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,ads
-	 -directoryServiceId=default,ou=config
-	changetype: modify
-	replace: ads-systemport
-	ads-systemport: 10637
-	-
-
-(here, we have modified the LDAPS Port from 10636 to 10637)
-
-Those modification can be done directly on the _config.ldif_ file, but you won't have any syntax check if you do so.
\ No newline at end of file
+# 3.1 - Authentication options
\ No newline at end of file

Modified: directory/site/trunk/content/apacheds/basic-ug/3.2-basic-authorization.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/3.2-basic-authorization.mdtext?rev=1403441&r1=1403440&r2=1403441&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/basic-ug/3.2-basic-authorization.mdtext (original)
+++ directory/site/trunk/content/apacheds/basic-ug/3.2-basic-authorization.mdtext Mon Oct 29 17:34:36 2012
@@ -1,8 +1,10 @@
-Title: 1.4.1 - Changing the server port for LDAP
-NavUp: 1.4-basic-configuration-tasks.html
-NavUpText: 1.4 - Basic configuration tasks
-NavNext: 1.4.2-changing-admin-password.html
-NavNextText: 1.4.2 - Changing the admin password
+Title: 3.2 - Basic authorization
+Navprev: 3.1-authentication-options.html
+NavPrevText: 3.1 - Authentication options
+NavUp: 3-basic-security.html
+NavUpText: 3 - Basic Security
+NavNext: 3.3-enabling-ssl.html
+NavNextText: 3.3 - How to enable SSL
 Notice: Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
     distributed with this work for additional information
@@ -20,112 +22,4 @@ Notice: Licensed to the Apache Software 
     specific language governing permissions and limitations
     under the License.
 
-# 1.4.1 - Changing the server port for LDAP
-
-This section describes how to change to port for the LDAP protocol. There are two ways to do that : either you use the configuration plugin available in **Apache Directory Studio**, or you update the LDIF partition that contains the configuration.
-
-[TOC]
-
-## The task and how to accomplish it
-
-By default the LDAP server listens on port 10389 (unencrypted or StartTLS) and 10636 (SSL). It is quite common to run LDAP on 389, which is the well-known port for this protocol, but that requires the server to be started with a root user (or with sudo). Of course other options are imaginable as well. Changing the LDAP port is a good example for adjusting the existing Spring configuration as introduced in the last section.
-
-<DIV class="note" markdown="1">
-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.
-</DIV>
-
-
-Basically, there are two cases :
-* The server is not started
-* The server is started
-
-We will see how to change the port in those two cases.
-
-### Using Apache Directory Studio
-
-#### The server is started
-
-The best solution is to connect on the server using Studio, and to open it's configuration :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config1.png)
-</CENTER>
-
-When you select this menu, you will get the main configuration screen, containing the port for LDAP and LDAPS :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-
-Now, change the values of _port_ to your needs, then save the configuration. You have to restart the server afterwards in order to take this change into effect.
-
-#### The server is not started
-
-You can start it and update the configuration, of course. But if you want to configure the server when it's stopped, you will have to load the configuration file, which is on _.../instances/default/conf/config.ldif_, when the server has been installed using the default setting.
-
-Opening this file will open the exact same window :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-You can update the _ports_ and save the file.
-
-<DIV class="warning" markdown="1">
-	Note that you will requite write access on this file !
-</DIV>
-
-### Modifying the configuration LDIF partition
-
-All the **ApacheDS** configuration is stored as a LDIF file, and can be modified either using a text editor (although we don't consider this as a safe practice) or using a Modify request on a running server. 
-
-<DIV class="info" markdown="1">
-	Modifying the configuration on a running server will **not** change the listening port of the running server. You will have to relaunch the server in order to get this new configuration to be available.
-</DIV>
-
-
-The configuration is stored as a set of LDAP entries, so you can update one of them. In order to modify the entry containing the ports, you have first to find it, and second to send a valid modify request.
-
-All the **ApacheDS** configuration is stored under the _ou=config_ partition. The ports are stored in some entries under _DN: ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ads-directoryServiceId=default,ou=config_ (obviously, dependning on your installation, this DN might change : the _ads-directoryServiceId_ may have a different name, so is the _ads-serverId_). In any case, the _ou=transports_ branch contains two entries :
-
-for LDAP :
-
-	dn: ads-transportid=ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ad
-	 s-directoryServiceId=default,ou=config
-	ads-systemport: 10389
-	ads-enabled: TRUE
-	ads-transportnbthreads: 8
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldap
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	 
-and for LDAPS :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,a
-	 ds-directoryServiceId=default,ou=config
-	ads-systemport: 10636
-	ads-transportenablessl: TRUE
-	ads-enabled: TRUE
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldaps
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	
-You just have to send a ModifyRequest using such a LDIF :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,ads
-	 -directoryServiceId=default,ou=config
-	changetype: modify
-	replace: ads-systemport
-	ads-systemport: 10637
-	-
-
-(here, we have modified the LDAPS Port from 10636 to 10637)
-
-Those modification can be done directly on the _config.ldif_ file, but you won't have any syntax check if you do so.
\ No newline at end of file
+# 3.2 - Basic authorization
\ No newline at end of file

Modified: directory/site/trunk/content/apacheds/basic-ug/3.3-enabling-ssl.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/3.3-enabling-ssl.mdtext?rev=1403441&r1=1403440&r2=1403441&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/basic-ug/3.3-enabling-ssl.mdtext (original)
+++ directory/site/trunk/content/apacheds/basic-ug/3.3-enabling-ssl.mdtext Mon Oct 29 17:34:36 2012
@@ -1,8 +1,10 @@
-Title: 1.4.1 - Changing the server port for LDAP
-NavUp: 1.4-basic-configuration-tasks.html
-NavUpText: 1.4 - Basic configuration tasks
-NavNext: 1.4.2-changing-admin-password.html
-NavNextText: 1.4.2 - Changing the admin password
+Title: 3.3 - How to enable SSL
+Navprev: 3.2-basic-authorization.html
+NavPrevText: 3.2 - Basic authorization
+NavUp: 3-basic-security.html
+NavUpText: 3 - Basic Security
+NavNext: 4-integrating-apacheds.html
+NavNextText: 4 - Integrating ApacheDS with other programs
 Notice: Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
     distributed with this work for additional information
@@ -20,112 +22,4 @@ Notice: Licensed to the Apache Software 
     specific language governing permissions and limitations
     under the License.
 
-# 1.4.1 - Changing the server port for LDAP
-
-This section describes how to change to port for the LDAP protocol. There are two ways to do that : either you use the configuration plugin available in **Apache Directory Studio**, or you update the LDIF partition that contains the configuration.
-
-[TOC]
-
-## The task and how to accomplish it
-
-By default the LDAP server listens on port 10389 (unencrypted or StartTLS) and 10636 (SSL). It is quite common to run LDAP on 389, which is the well-known port for this protocol, but that requires the server to be started with a root user (or with sudo). Of course other options are imaginable as well. Changing the LDAP port is a good example for adjusting the existing Spring configuration as introduced in the last section.
-
-<DIV class="note" markdown="1">
-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.
-</DIV>
-
-
-Basically, there are two cases :
-* The server is not started
-* The server is started
-
-We will see how to change the port in those two cases.
-
-### Using Apache Directory Studio
-
-#### The server is started
-
-The best solution is to connect on the server using Studio, and to open it's configuration :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config1.png)
-</CENTER>
-
-When you select this menu, you will get the main configuration screen, containing the port for LDAP and LDAPS :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-
-Now, change the values of _port_ to your needs, then save the configuration. You have to restart the server afterwards in order to take this change into effect.
-
-#### The server is not started
-
-You can start it and update the configuration, of course. But if you want to configure the server when it's stopped, you will have to load the configuration file, which is on _.../instances/default/conf/config.ldif_, when the server has been installed using the default setting.
-
-Opening this file will open the exact same window :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-You can update the _ports_ and save the file.
-
-<DIV class="warning" markdown="1">
-	Note that you will requite write access on this file !
-</DIV>
-
-### Modifying the configuration LDIF partition
-
-All the **ApacheDS** configuration is stored as a LDIF file, and can be modified either using a text editor (although we don't consider this as a safe practice) or using a Modify request on a running server. 
-
-<DIV class="info" markdown="1">
-	Modifying the configuration on a running server will **not** change the listening port of the running server. You will have to relaunch the server in order to get this new configuration to be available.
-</DIV>
-
-
-The configuration is stored as a set of LDAP entries, so you can update one of them. In order to modify the entry containing the ports, you have first to find it, and second to send a valid modify request.
-
-All the **ApacheDS** configuration is stored under the _ou=config_ partition. The ports are stored in some entries under _DN: ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ads-directoryServiceId=default,ou=config_ (obviously, dependning on your installation, this DN might change : the _ads-directoryServiceId_ may have a different name, so is the _ads-serverId_). In any case, the _ou=transports_ branch contains two entries :
-
-for LDAP :
-
-	dn: ads-transportid=ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ad
-	 s-directoryServiceId=default,ou=config
-	ads-systemport: 10389
-	ads-enabled: TRUE
-	ads-transportnbthreads: 8
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldap
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	 
-and for LDAPS :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,a
-	 ds-directoryServiceId=default,ou=config
-	ads-systemport: 10636
-	ads-transportenablessl: TRUE
-	ads-enabled: TRUE
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldaps
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	
-You just have to send a ModifyRequest using such a LDIF :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,ads
-	 -directoryServiceId=default,ou=config
-	changetype: modify
-	replace: ads-systemport
-	ads-systemport: 10637
-	-
-
-(here, we have modified the LDAPS Port from 10636 to 10637)
-
-Those modification can be done directly on the _config.ldif_ file, but you won't have any syntax check if you do so.
\ No newline at end of file
+# 3.3 - How to enable SSL
\ No newline at end of file

Modified: directory/site/trunk/content/apacheds/basic-ug/4-integrating-apacheds.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/4-integrating-apacheds.mdtext?rev=1403441&r1=1403440&r2=1403441&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/basic-ug/4-integrating-apacheds.mdtext (original)
+++ directory/site/trunk/content/apacheds/basic-ug/4-integrating-apacheds.mdtext Mon Oct 29 17:34:36 2012
@@ -1,8 +1,8 @@
-Title: 1.4.1 - Changing the server port for LDAP
-NavUp: 1.4-basic-configuration-tasks.html
-NavUpText: 1.4 - Basic configuration tasks
-NavNext: 1.4.2-changing-admin-password.html
-NavNextText: 1.4.2 - Changing the admin password
+Title: 4 - Integrating ApacheDS with other programs
+Navprev: 3-basic-security.html
+NavPrevText: 3 - Basic Security
+NavUp: ../basic-users-guide.html
+NavUpText: Basic User Guide
 Notice: Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
     distributed with this work for additional information
@@ -20,112 +20,4 @@ Notice: Licensed to the Apache Software 
     specific language governing permissions and limitations
     under the License.
 
-# 1.4.1 - Changing the server port for LDAP
-
-This section describes how to change to port for the LDAP protocol. There are two ways to do that : either you use the configuration plugin available in **Apache Directory Studio**, or you update the LDIF partition that contains the configuration.
-
-[TOC]
-
-## The task and how to accomplish it
-
-By default the LDAP server listens on port 10389 (unencrypted or StartTLS) and 10636 (SSL). It is quite common to run LDAP on 389, which is the well-known port for this protocol, but that requires the server to be started with a root user (or with sudo). Of course other options are imaginable as well. Changing the LDAP port is a good example for adjusting the existing Spring configuration as introduced in the last section.
-
-<DIV class="note" markdown="1">
-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.
-</DIV>
-
-
-Basically, there are two cases :
-* The server is not started
-* The server is started
-
-We will see how to change the port in those two cases.
-
-### Using Apache Directory Studio
-
-#### The server is started
-
-The best solution is to connect on the server using Studio, and to open it's configuration :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config1.png)
-</CENTER>
-
-When you select this menu, you will get the main configuration screen, containing the port for LDAP and LDAPS :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-
-Now, change the values of _port_ to your needs, then save the configuration. You have to restart the server afterwards in order to take this change into effect.
-
-#### The server is not started
-
-You can start it and update the configuration, of course. But if you want to configure the server when it's stopped, you will have to load the configuration file, which is on _.../instances/default/conf/config.ldif_, when the server has been installed using the default setting.
-
-Opening this file will open the exact same window :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-You can update the _ports_ and save the file.
-
-<DIV class="warning" markdown="1">
-	Note that you will requite write access on this file !
-</DIV>
-
-### Modifying the configuration LDIF partition
-
-All the **ApacheDS** configuration is stored as a LDIF file, and can be modified either using a text editor (although we don't consider this as a safe practice) or using a Modify request on a running server. 
-
-<DIV class="info" markdown="1">
-	Modifying the configuration on a running server will **not** change the listening port of the running server. You will have to relaunch the server in order to get this new configuration to be available.
-</DIV>
-
-
-The configuration is stored as a set of LDAP entries, so you can update one of them. In order to modify the entry containing the ports, you have first to find it, and second to send a valid modify request.
-
-All the **ApacheDS** configuration is stored under the _ou=config_ partition. The ports are stored in some entries under _DN: ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ads-directoryServiceId=default,ou=config_ (obviously, dependning on your installation, this DN might change : the _ads-directoryServiceId_ may have a different name, so is the _ads-serverId_). In any case, the _ou=transports_ branch contains two entries :
-
-for LDAP :
-
-	dn: ads-transportid=ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ad
-	 s-directoryServiceId=default,ou=config
-	ads-systemport: 10389
-	ads-enabled: TRUE
-	ads-transportnbthreads: 8
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldap
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	 
-and for LDAPS :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,a
-	 ds-directoryServiceId=default,ou=config
-	ads-systemport: 10636
-	ads-transportenablessl: TRUE
-	ads-enabled: TRUE
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldaps
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	
-You just have to send a ModifyRequest using such a LDIF :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,ads
-	 -directoryServiceId=default,ou=config
-	changetype: modify
-	replace: ads-systemport
-	ads-systemport: 10637
-	-
-
-(here, we have modified the LDAPS Port from 10636 to 10637)
-
-Those modification can be done directly on the _config.ldif_ file, but you won't have any syntax check if you do so.
\ No newline at end of file
+# 4 - Integrating ApacheDS with other programs
\ No newline at end of file

Modified: directory/site/trunk/content/apacheds/basic-ug/4.1-mozilla-thunderbird.mdtext
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/4.1-mozilla-thunderbird.mdtext?rev=1403441&r1=1403440&r2=1403441&view=diff
==============================================================================
--- directory/site/trunk/content/apacheds/basic-ug/4.1-mozilla-thunderbird.mdtext (original)
+++ directory/site/trunk/content/apacheds/basic-ug/4.1-mozilla-thunderbird.mdtext Mon Oct 29 17:34:36 2012
@@ -1,8 +1,8 @@
-Title: 1.4.1 - Changing the server port for LDAP
-NavUp: 1.4-basic-configuration-tasks.html
-NavUpText: 1.4 - Basic configuration tasks
-NavNext: 1.4.2-changing-admin-password.html
-NavNextText: 1.4.2 - Changing the admin password
+Title: 4.1 - Mozilla Thunderbird
+Navprev: 4-integrating-apacheds.html
+NavPrevText: 4 - Integrating ApacheDS with other programs
+NavUp: 4-integrating-apacheds.html
+NavUpText: 4 - Integrating ApacheDS with other programs
 Notice: Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
     distributed with this work for additional information
@@ -20,112 +20,4 @@ Notice: Licensed to the Apache Software 
     specific language governing permissions and limitations
     under the License.
 
-# 1.4.1 - Changing the server port for LDAP
-
-This section describes how to change to port for the LDAP protocol. There are two ways to do that : either you use the configuration plugin available in **Apache Directory Studio**, or you update the LDIF partition that contains the configuration.
-
-[TOC]
-
-## The task and how to accomplish it
-
-By default the LDAP server listens on port 10389 (unencrypted or StartTLS) and 10636 (SSL). It is quite common to run LDAP on 389, which is the well-known port for this protocol, but that requires the server to be started with a root user (or with sudo). Of course other options are imaginable as well. Changing the LDAP port is a good example for adjusting the existing Spring configuration as introduced in the last section.
-
-<DIV class="note" markdown="1">
-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.
-</DIV>
-
-
-Basically, there are two cases :
-* The server is not started
-* The server is started
-
-We will see how to change the port in those two cases.
-
-### Using Apache Directory Studio
-
-#### The server is started
-
-The best solution is to connect on the server using Studio, and to open it's configuration :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config1.png)
-</CENTER>
-
-When you select this menu, you will get the main configuration screen, containing the port for LDAP and LDAPS :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-
-Now, change the values of _port_ to your needs, then save the configuration. You have to restart the server afterwards in order to take this change into effect.
-
-#### The server is not started
-
-You can start it and update the configuration, of course. But if you want to configure the server when it's stopped, you will have to load the configuration file, which is on _.../instances/default/conf/config.ldif_, when the server has been installed using the default setting.
-
-Opening this file will open the exact same window :
-
-<CENTER>
-![Studio port configuration](images/studio-port-config2.png)
-</CENTER>
-
-You can update the _ports_ and save the file.
-
-<DIV class="warning" markdown="1">
-	Note that you will requite write access on this file !
-</DIV>
-
-### Modifying the configuration LDIF partition
-
-All the **ApacheDS** configuration is stored as a LDIF file, and can be modified either using a text editor (although we don't consider this as a safe practice) or using a Modify request on a running server. 
-
-<DIV class="info" markdown="1">
-	Modifying the configuration on a running server will **not** change the listening port of the running server. You will have to relaunch the server in order to get this new configuration to be available.
-</DIV>
-
-
-The configuration is stored as a set of LDAP entries, so you can update one of them. In order to modify the entry containing the ports, you have first to find it, and second to send a valid modify request.
-
-All the **ApacheDS** configuration is stored under the _ou=config_ partition. The ports are stored in some entries under _DN: ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ads-directoryServiceId=default,ou=config_ (obviously, dependning on your installation, this DN might change : the _ads-directoryServiceId_ may have a different name, so is the _ads-serverId_). In any case, the _ou=transports_ branch contains two entries :
-
-for LDAP :
-
-	dn: ads-transportid=ldap,ou=transports,ads-serverId=ldapServer,ou=servers,ad
-	 s-directoryServiceId=default,ou=config
-	ads-systemport: 10389
-	ads-enabled: TRUE
-	ads-transportnbthreads: 8
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldap
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	 
-and for LDAPS :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,a
-	 ds-directoryServiceId=default,ou=config
-	ads-systemport: 10636
-	ads-transportenablessl: TRUE
-	ads-enabled: TRUE
-	ads-transportaddress: 0.0.0.0
-	ads-transportid: ldaps
-	objectclass: ads-transport
-	objectclass: ads-tcpTransport
-	objectclass: ads-base
-	objectclass: top
-	
-You just have to send a ModifyRequest using such a LDIF :
-
-	dn: ads-transportid=ldaps,ou=transports,ads-serverId=ldapServer,ou=servers,ads
-	 -directoryServiceId=default,ou=config
-	changetype: modify
-	replace: ads-systemport
-	ads-systemport: 10637
-	-
-
-(here, we have modified the LDAPS Port from 10636 to 10637)
-
-Those modification can be done directly on the _config.ldif_ file, but you won't have any syntax check if you do so.
\ No newline at end of file
+# 4.1 - Mozilla Thunderbird
\ No newline at end of file

Added: directory/site/trunk/content/apacheds/basic-ug/images/w32_service_properties.png
URL: http://svn.apache.org/viewvc/directory/site/trunk/content/apacheds/basic-ug/images/w32_service_properties.png?rev=1403441&view=auto
==============================================================================
Binary file - no diff available.

Propchange: directory/site/trunk/content/apacheds/basic-ug/images/w32_service_properties.png
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream



Mime
View raw message