Return-Path: X-Original-To: apmail-directory-commits-archive@www.apache.org Delivered-To: apmail-directory-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4E77F10AE5 for ; Sat, 29 Nov 2014 22:40:40 +0000 (UTC) Received: (qmail 27654 invoked by uid 500); 29 Nov 2014 22:40:40 -0000 Delivered-To: apmail-directory-commits-archive@directory.apache.org Received: (qmail 27605 invoked by uid 500); 29 Nov 2014 22:40:40 -0000 Mailing-List: contact commits-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@directory.apache.org Delivered-To: mailing list commits@directory.apache.org Received: (qmail 27596 invoked by uid 99); 29 Nov 2014 22:40:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Nov 2014 22:40:40 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,URIBL_DBL_ABUSE_REDIR,URIBL_DBL_REDIR X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 29 Nov 2014 22:40:37 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 418262389177 for ; Sat, 29 Nov 2014 22:40:17 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r931016 - in /websites/staging/directory/trunk/content: ./ apacheds/advanced-ug/2-server-config.html apacheds/advanced-ug/2.2-installation-layout.html apacheds/advanced-ug/2.2.1-debian-installation-layout.html Date: Sat, 29 Nov 2014 22:40:17 -0000 To: commits@directory.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20141129224017.418262389177@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: buildbot Date: Sat Nov 29 22:40:16 2014 New Revision: 931016 Log: Staging update by buildbot for directory Added: websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2.1-debian-installation-layout.html Modified: websites/staging/directory/trunk/content/ (props changed) websites/staging/directory/trunk/content/apacheds/advanced-ug/2-server-config.html websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2-installation-layout.html Propchange: websites/staging/directory/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Sat Nov 29 22:40:16 2014 @@ -1 +1 @@ -1642408 +1642480 Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/2-server-config.html ============================================================================== --- websites/staging/directory/trunk/content/apacheds/advanced-ug/2-server-config.html (original) +++ websites/staging/directory/trunk/content/apacheds/advanced-ug/2-server-config.html Sat Nov 29 22:40:16 2014 @@ -170,7 +170,14 @@

Chapter content

Modified: websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2-installation-layout.html ============================================================================== --- websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2-installation-layout.html (original) +++ websites/staging/directory/trunk/content/apacheds/advanced-ug/2.2-installation-layout.html Sat Nov 29 22:40:16 2014 @@ -165,150 +165,16 @@

2.2 - Installation Layout

-

When you installed ApacheDS on your machine, it created various directories on your disk. Typically, we need to store :

+

When you installed ApacheDS on your machine, it created various directories on your disk. Those created directories, and the files we put in them, are machine dependent.

+

The following chapters will describe the installation layout for the various OS we support :

+

Note that the installation will differ with the target OS. We currently support :

-

We will describe in this chapter the global layout and the various files and their meaning and use. Note that the installation will differ with the target OS. We currently support :

-
    -
  • debian debian
  • -
  • RPM readHat RPM
  • -
  • windows windows
  • -
  • MacOSX Mac OSX
  • -
-

We also provide two packages, one which is a binary package that should run as is on any linux box, but will not be started as a daemon, and another which contains all the files.

-

In the next paragraph, we will describe the installation layout for each OS.

-

debian Debian Standard layout

-

On debian, the installation will be done in /opt, and the daemon script will be in /etc/init.d. Here are the created directories :

-
-  /opt
-    |
-    +-- bin/
-    |    |
-    |    +-- apacheds*
-    |    |
-    |    +-- wrapper*
-    |
-    +-- conf/
-    |    |
-    |    +-- wrapper.conf
-    |
-    +-- lib/
-    |    |
-    |    +-- apacheds-service-.jar
-    |    |
-    |    +-- apacheds-wrapper-.jar
-    |    |
-    |    +-- libwrapper.so
-    |    |
-    |    +-- wrapper-3.2.3.jar
-    |
-    +-- NOTICE
-    |
-    +-- LICENSE
-
- -

Starting ther server

-

THere are three ways to start the server :

-
    -
  • as a daemon : in this case, the server is automatically started when the machine is started.
  • -
  • starting the daemon from /etc/init.d manually
  • -
  • starting the server from /opt/apacheds-/bin
  • -
-

The most convenient is obviously to let the server starts apacheDS automatically when the server is started. It's enough to launch this command once the installation has been done :

-
$ sudo su
-$ cd /etc/init.d
-$ update-rc.d apacheds-2.0.0-M20-default defaults
-Adding system startup for /etc/init.d/apacheds-2.0.0-M20-default ...
-/etc/rc0.d/K20apacheds-2.0.0-M20-default -> ../init.d/apacheds-2.0.0-M20-default
-/etc/rc1.d/K20apacheds-2.0.0-M20-default -> ../init.d/apacheds-2.0.0-M20-default
-/etc/rc6.d/K20apacheds-2.0.0-M20-default -> ../init.d/apacheds-2.0.0-M20-default
-/etc/rc2.d/S20apacheds-2.0.0-M20-default -> ../init.d/apacheds-2.0.0-M20-default
-/etc/rc3.d/S20apacheds-2.0.0-M20-default -> ../init.d/apacheds-2.0.0-M20-default
-/etc/rc4.d/S20apacheds-2.0.0-M20-default -> ../init.d/apacheds-2.0.0-M20-default
-/etc/rc5.d/S20apacheds-2.0.0-M20-default -> ../init.d/apacheds-2.0.0-M20-default
-
- - -

Otherwise, starting the server using option 2 is all about typing this command line :

-
$ sudo /etc/init.d/apacheds-2.0.0-M20-default start
-
- - -

This will start the default instance. Would you like to have more than one instance of the server installed, then you'll have to modify this script.

-

Starting the server using the apacheds script requires that you provide a third parameter : the instance to run.

-
$ sudo /opt/apacheds-2.0.0-M20/bin/apacheds start default
-
- - -

bin directory

-

The bin directory contains the binary used to launch the server. The apacheds script starts the wrapper executable, using the configuration file wrapper.conf.

-

conf directory

-

This directory contain the wrapper configuration file. This is a description of its content.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
parameterDescriptionDefault value
wrapper.java.maxmemoryThe -Xmx JVM parameter2048m
wrapper.ping.timeoutThe delay after which we will consider the server as stalled240s (4 mins)
wrapper.startup.timeoutThe maximum delay allowed for the server to start120 secs