org.forgerock / org.forgerock.opendj

12 Jun, 2007

1 commit

08 May, 2007

2 commits

07 May, 2007

1 commit

26 Apr, 2007

1 commit

25 Apr, 2007

1 commit

  • 5ef39a99   Fix for issue 1273 (exception if JAVA_HOME undefined in scripts). ... Browse Dir » 
    The fix consists of modifying the scripts to launch the InstallDS classwith a test option using the JVM
 that was found.  If the JVM can be successfully launched, the JVM is compatible with 1.5, if not we as
sume that is not compatible with JDK 1.5.

The downside of the fix is that it requires an additional start of the JVM each time the command line i
s launched. That is why the fix only applies to setup, uninstall, upgrade, start and stop command lines.  The modifications in _server-script.* and _client-script.sh just modify the message displayed when a JVM could not be found (informing that JDK 1.5 or later can be used).


git-svn-id: https://svn.forgerock.org/opendj/trunk@1701 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

10 Apr, 2007

1 commit

  • 59b9d1d7   Added the following capabilities to OpenDS: ... Browse Dir » 
    - Index rebuilding capabilities. All indexes including system and attribute indexes can 
be rebuilt. Each index will be rebuilt by a seperate thread to increase performance. A 
max number of rebuild threads could be set to limit the resources used by large rebuild 
jobs. Partial rebuilds of attribute indexes could also be done by specifying the 
attribute index type after the attribute type (ie. sn.approximate).
- Index rebuilding standalone tool. Rebuilding of attribute indexes could be done with 
the backend online. However, rebuilds including system indexes must be done with the 
backend offline.
- Index rebuilding task. Rebuilding of attribute indexes are done with the backend 
online. Rebuilds that include system indexes will be performed after bring the backend 
offline. The user must have index-rebuild privilages to rebuild indexes.
- Approxitae indexing capability. The value of the attribute will be normalized using 
the approximate maching rule of that attribute type. This is used as the key for the 
index. Approximate indexes are fully supported by the index verify, rebuild, and import 
jobs.
- Fixed bug in build.xml where weave is enabled even if a test.* property is set.
- Consolidated some common tool messages.
- Consolidated some JE backend methods common to all tools.
- Added unit tests for rebuild job and approximate indexes.

Fix for issues 35, 39, 40, 41


git-svn-id: https://svn.forgerock.org/opendj/trunk@1607 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     

04 Apr, 2007

1 commit

  • 7bb9469f   Fix CLI consistency ... Browse Dir » 
    issues: 1407 1408 1410 1411 1412 1413 1414 1416 1417 1418 1419 1420 1421

git-svn-id: https://svn.forgerock.org/opendj/trunk@1565 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     

26 Mar, 2007

1 commit

16 Mar, 2007

1 commit

15 Mar, 2007

1 commit

  • 3c4a2403   Fix for issue 528 (Windows Service Definition for Automatic Startup). ... Browse Dir » 
    The following changes are targeted to be able to run OpenDS as a windows 
service.

The idea is to be able to run OpenDS to run as a service and to be able 
also to disable this feature.

The setup has been updated to run OpenDS as a service in windows (which 
is the standard behavior in this platform).  The uninstall has also been 
updated to remove all references to OpenDS in the Registry and in the 
list of services once OpenDS has been uninstalled.

A new executable (opends_service.exe) has been added to be able to 
perform all the tasks that require native code 
(registering/unregistering the service, sending events to the event log, 
etc.).  Most of the code required by this executable is in the file 
service.c.  The README file has been updated and a Makefile file 
provided to generate all the executables.

A new command line has been added: windowsservice.bat.  The usage of 
this command line is the following one:

This utility may be used to configure OpenDS as a Windows service.
Usage:  windowsservice {options}
              where {options} include:
-e  or   --enableService
     Enables OpenDS as a Windows service.
-d  or   --disableService
     Disables OpenDS as a Windows service and stops the server
-s  or   --serviceState
     Provides information about the state of OpenDS as a Windows service.
-H  or   --help
     Display this usage information.

The class associated with this command line (ConfigureWindowsService) 
uses opends_service.exe.  ConfigureWindowsService is basically a wrapper 
that allows to have the messages displayed to the user in the Java code 
(and so to minimize what is done by the native code).


Some changes have been made in the start-ds(.bat) and stop-ds(.bat) 
scripts by extending what the --checkStartability (in DirectoryServer 
class) and --checkStoppability (in StopDS class) do.  I think that it is 
a good idea to have all the parsing of the arguments into the java code 
(specially considering the limitations of the .bat files).  So I have 
moved most of the parsing to the java code so that the is the java code 
that provides a return code to the scripts to tell them what to do 
(start the server in detach mode, stop the server using a system call, 
stop the server using protocol, etc.).

In the particular case of how start-ds.bat and stop-ds.bat have been 
updated to manage the case where the server must be started using the 
system call 'net start <service_name>' and 'net stop <service_name>'. 
--checkstoppability and --checkstartability tell whether the server must 
be stopped/started directly with a system call (or stopped using LDAP 
protocol) or using the Windows Service system.  If it is the latter the 
bat files use two new auxiliary classes (StopWindowsService and 
StartWindowsService).  These classes figure out the service name 
associated with the OpenDS instance and call net stop (or net start) 
using that service name.

When net start/net stop are called start-ds.bat (or stop-ds.bat) are 
called.  The Windows Services have been configured to call start-ds.bat 
and stop-ds.bat with some particular options (--windowsNetStart and 
--windowsNetStop) to identify the case where we must start/stop the 
server directly (and so not having an infinite recursive loop of calls 
to net start/net stop).

In order to have the same user experience when the server is configured 
to run as a service and when is not the tool class WaitForDelete has 
also been updated to write its output to a file.  This has been done 
because piping from the standard output to a file in the context of a 
Windows Service call does not seem to work properly.  So now 
WaitForDelete has a new option --outputFile.

setup --cli on windows has a new option '-n' or '-noWindowsService' to allow not to enable the windows service.  When run in interactive mode and this options is not specified the user will systematically be asked whether to enable the windows service or not. 



git-svn-id: https://svn.forgerock.org/opendj/trunk@1418 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

01 Mar, 2007

1 commit

27 Feb, 2007

1 commit

  • 91bff36a   The proposed fix is to do a similar thing that what has been done by ... Browse Dir » 
    Neil for issue #1266:  use a hidden option to check whether the server
is already running or not.  If the server is not running the message
'Server already stopped' is displayed, if the server is running the message 'Stopping Server... is displayed'.

So the output of the command with this changes is:

If the server is running
========================

bash-3.00$ bin/stop-ds --restart
Stopping Server...

[23/Feb/2007:17:00:28 +0100] category=CORE severity=NOTICE id=458886
msg="OpenDS Directory Server 0.1.0 starting up."
[23/Feb/2007:17:00:34 +0100] category=BACKEND severity=NOTICE id=8847402
msg="A database backend containing 1 entries has started."
[23/Feb/2007:17:00:34 +0100] category=CONFIG severity=SEVERE_WARNING
id=3277325 msg="Access control has been disabled."
[23/Feb/2007:17:00:35 +0100] category=CORE severity=NOTICE id=458887
msg="The Directory Server has started successfully."
[23/Feb/2007:17:00:35 +0100] category=CORE severity=NOTICE id=458891
msg="The Directory Server has sent an alert notification generated by
class org.opends.server.core.DirectoryServer (alert type
org.opends.server.DirectoryServerStarted, alert ID 458887):  The
Directory Server has started successfully.."
bash-3.00$
bash-3.00$ bin/stop-ds



If the server is stopped
========================

bash-3.00$ bin/stop-ds
Server already stopped.
bash-3.00$ bin/stop-ds --restart
Server already stopped.
[23/Feb/2007:16:59:50 +0100] category=CORE severity=NOTICE id=458886
msg="OpenDS Directory Server 0.1.0 starting up."
[23/Feb/2007:16:59:55 +0100] category=BACKEND severity=NOTICE id=8847402
msg="A database backend containing 1 entries has started."
[23/Feb/2007:16:59:56 +0100] category=CONFIG severity=SEVERE_WARNING
id=3277325 msg="Access control has been disabled."
[23/Feb/2007:16:59:57 +0100] category=CORE severity=NOTICE id=458887
msg="The Directory Server has started successfully."
[23/Feb/2007:16:59:57 +0100] category=CORE severity=NOTICE id=458891
msg="The Directory Server has sent an alert notification generated by
class org.opends.server.core.DirectoryServer (alert type
org.opends.server.DirectoryServerStarted, alert ID 458887):  The
Directory Server has started successfully.." 


git-svn-id: https://svn.forgerock.org/opendj/trunk@1263 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

23 Feb, 2007

1 commit

  • 11a1cf3b   Fix for issue 1271. ... Browse Dir » 
    "%*" Does not work properly when we have arguments with quotes.  Use a FOR statement to determine whether the user provided arguments or not to the stop-ds.bat command. 


git-svn-id: https://svn.forgerock.org/opendj/trunk@1233 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

22 Feb, 2007

5 commits

  • 06d7d1f5   This fixes a bug when the user provides only one parameter (-R or --restart). ... Browse Dir » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@1227 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • f7068255   If the user provides no arguments or only the -R argument, we will assume that ... Browse Dir » 
    we want to stop the local server an we use the pid to kill it.  If other
arguments are passed (which appart from --help are arguments related to LDAP
authentication) I will assume that we are trying to stop the server using
protocol.

This fixes issue 1261.


git-svn-id: https://svn.forgerock.org/opendj/trunk@1225 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 064d9cbb   Update the start-ds.bat batch file to use the --checkStartability option to ... Browse Dir » 
    properly handle the case where the server is already running.

OpenDS Issue Number:  1251


git-svn-id: https://svn.forgerock.org/opendj/trunk@1221 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • d4d0fcf8   Update the start-ds script and associated Directory Server code to ensure that ... Browse Dir » 
    the PID file is only written if the server is not already running.  If it's not
being used to try to start the server, then just invoke the command without a
PID file.  If it is trying to start the server but the server is already
running, then exit with an error.

OpenDS Issue Number:  1251


git-svn-id: https://svn.forgerock.org/opendj/trunk@1220 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 425747b6   Fix for Issues #1025 and #1248 ('stop-ds.bat should be able to stop server even … ... Browse Dir » 
    …if LDAP port' and 'cannot stop server through status panel').

The goal of these changes is to be able to have exactly the same user interface in Windows and Unix to stop the server.  In windows we force the user to provide LDAP credentials even if the command is going to be run locally.  The goal is to allow to stop the server using only system credentials (as we do in UNIX) when the user does not provide arguments when calling stop-ds.bat.

In order to do this I have written some native code.  This native code is called when we start the server to:
1. Launch the java process and get the associated PID.
2. Create a server.pid file as we do for UNIX systems to store the PID of the process.

The native code that stops the server reads the PID file contents and tries to stop the process associated with the PID.

In order to allow the users to be able to build the product with independence of the platform, the binaries will be included with the source code.  The code used to generate these binaries will also be provided.

I have generated 1 executable called winlauncher.exe.  The binaries will be committed in the source tree under lib (with activation.jar and mail.jar).  They will also be installed under <server root>\lib.

The native code is in the files winlauncher.c and winlauncher.h.  These files are placed under the new directory build-tools/src/windows.

I have tried to keep the native code simple and leave as much logic as I could into the batch files (for instance everything related to the discovery of the java binaries) so that the administrators can play with them.

A README file has been also been included to explain how to generate the binaries.

Extras:
When we call start-ds from the command line, the server will not stop when the command prompt window is closed (unless start-ds was called to run in not-detached mode).  The next step is to register DS as a service to avoid the server to be stopped when the user logs out.

When we call setup (with no arguments) or the statuspanel the generated process (and windows) will no longer get killed when the command prompt window is killed.

When the user double-clicks on the setup.bat or the statuspanel.bat files, the command prompt window only appears briefly.  Today when we do this a command prompt window stays open until we close setup or the status panel window.


git-svn-id: https://svn.forgerock.org/opendj/trunk@1218 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     

01 Feb, 2007

1 commit

28 Jan, 2007

1 commit

23 Jan, 2007

2 commits

05 Jan, 2007

1 commit

11 Dec, 2006

1 commit

13 Nov, 2006

2 commits

10 Nov, 2006

1 commit

  • a294922e   Make a number of changes to administrative tools provided with OpenDS. These ... Browse Dir » 
    are all made under the umbrella of issue #994, but there are individual issues
for each change.

- Issue #979 -- Re-order LDAP tool arguments
  When displaying usage information for many of the LDAP tools (e.g.,
  ldapsearch, ldapmodify, etc.), the arguments were not provided in any kind of
  logical grouping.  This has been corrected so that the arguments are listed
  in a more logical ordering.

- Issue #983 -- Add tool description to argument parser
  When displaying usage information for administrative tools, it now includes a
  small summary of what the tool does at the top of the argument list.

- Issue #984 -- Make tool usage more compact
  Previously, the tool usage included a blank line between each argument, which
  made the usage information seem too verbose, especially for tools like
  ldapsearch with a lot of arguments.  This extra space has been removed.
  Also, many of the argument descriptions have been rewritten in an attempt to
  avoid requiring multiple lines.

- Issue #985 -- Wrap long output in administrative tools when appropriate
  Update most of the output for the administrative tools so that it is easier
  to read on 80-column displays.  This primarily impacts error message, and
  cases in which the format of the output is important (e.g., LDIF output from
  ldapsearch) no changes were made.

- Issue #986 -- Eliminate hard-coded strings in tools
  Some of the tools had hard-coded strings used for error and warning messages.
  They have been replaced with localizeable output from the messages files.

- Issue #990 -- LDAP tools don't use trust store password
  The LDAP tools didn't provide any mechanism for specifying the PIN needed to
  access the contents of an SSL trust store.  Some types of trust stores may
  require a PIN to access them, so it is now possible to either directly
  specify the PIN or to provide the path to a PIN file.

- Issue #991 -- Disconnect when running stop-ds shouldn't be an error
  When using the stop-ds script, if the server began shutting down before it
  returned a response to the client, the client would provide an error message
  making it sound like something went wrong.  The output has now been updated
  to indicate that the server is likely in the course of shutting down.

- Issue #992 -- Tool usage should include the tool name rather than the class
  When displaying usage information for the administrative tools, the
  fully-qualified class name for the Java class was displayed, where the name
  of the shell script or batch file would have been more useful.


git-svn-id: https://svn.forgerock.org/opendj/trunk@702 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

08 Nov, 2006

2 commits

  • 49c58a7a   Make several property updates to administrative shell scripts and batch files: ... Browse Dir » 
    
- All administrative shell scripts and batch files now have the svn:eol-style
  property set to "native".  This property was not set for some of these files.

- All administrative shell scripts now have the svn:executable property set.
  Some of them did not have this property set and therefore did not have the
  executable file permission bit set.

- All administrative batch files now have the svn:executable property removed.
  Some batch files inadvertently had this property set.


OpenDS Issue Number:  970


git-svn-id: https://svn.forgerock.org/opendj/trunk@686 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 1bec92c1   Add a missing backup script that was inadvertently removed when all of the ... Browse Dir » 
    administrative shell scripts were renamed to drop the ".sh" extension.

OpenDS Issue Number:  967


git-svn-id: https://svn.forgerock.org/opendj/trunk@685 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

31 Oct, 2006

1 commit

  • f5384b01   Change the flag used to start the server in the foreground from "-nodetach" ... Browse Dir » 
    (with a single dash) to "--nodetach" (with two dashes).  It can also be used as
"-N" with a single dash.  This has the following benefits:

- It is more consistent with our other command-line arguments, and it is
  CLIP compliant.

- It makes it possible for the flag to appear anywhere in the argument list
  rather than just being the first argument.

- It makes it possible to provide this feature on Windows, whereas before it
  was only available on UNIX-based systems.

- On UNIX-based systems, "--nodetach" is now case-insensitive, although it is
  case-sensitive (all lowercase) on Windows systems.  The "-N" alternative is
  always case sensitive.

OpenDS Issue Number:  900


git-svn-id: https://svn.forgerock.org/opendj/trunk@664 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

30 Oct, 2006

1 commit

29 Oct, 2006

1 commit

28 Oct, 2006

1 commit

  • 618f29aa   fix for issue 893 ... Browse Dir » 
    the batch files just needed a couple of double-quotes

git-svn-id: https://svn.forgerock.org/opendj/trunk@645 41b1ffd8-f28e-4786-ab96-9950f0a78031
    al_xipe
     

27 Oct, 2006

1 commit

  • f93b9d44   Make a number of changes to administrative batch files for Windows systems: ... Browse Dir » 
    - Update the start-ds.bat file so that it starts in the background rather than
  the foreground, and will not exit until the server has actually started.
  Issue #590.

- Update all of the batch files to explicitly set the PATH for better
  consistency and security.  Issue #607.

- Consolidate a lot of the content into _client-script.bat and 
  _server-script.bat files to make the batch files more maintainable.
  Issue #873.


git-svn-id: https://svn.forgerock.org/opendj/trunk@643 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

25 Oct, 2006

1 commit

  • 474f1eca   Make several changes to administrative shell scripts provided with OpenDS. ... Browse Dir » 
    All of these changes fall under the blanket of issue 882, but are also
associated with a number of individual sub-issues.

The changes include:

- Create new "_client-script.sh" and "_server-script.sh" shell scripts that
  hold the majority of the logic required to launch the client-side and
  server-side tools (Issue #873).

- Explicitly set the PATH, LD_LIBRARY_PATH, and LD_PRELOAD (and the 32-bit and
  64-bit specific variants of LD_LIBRARY_PATH and LD_PRELOAD) to ensure better
  security and more consistent behavior when invoking external commands
  (Issue #607).

- Fix potential problems that could arise if either OpenDS or the Java runtime
  are installed in a path that contains spaces (Issue #820).

- Update the start-ds.sh script so that it always creates a PID file, whether
  running in the foreground or in the background (Issue #859).

- Update the start-ds.sh script so that when running in the background it will
  not exit until it confirms that the server is actually running.  It will also
  display any messages written to standard output/standard error during
  startup (Issue #590).

- Update the stop-ds.sh script so that it can either perform a local stop (via
  kill with the TERM signal) or a remote stop (over LDAP using the shutdown
  task).  If the script is invoked with no arguments and there is a local PID
  file present, then it will be a local stop via kill, and it will wait until
  the server actually has stopped before exiting.  Otherwise it will be a
  remote stop over LDAP (Issue #871).


git-svn-id: https://svn.forgerock.org/opendj/trunk@640 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

14 Oct, 2006

1 commit

13 Oct, 2006

1 commit

07 Sep, 2006

1 commit

  • 4e5103f0   Add a new ldifmodify tool that works like ldapmodify except that it alters data ... Browse Dir » 
    in an LDIF file rather than over LDAP.  There are some limitations, including:

- Modify DN operations are not supported
- Operations that would attempt to delete or alter an entry after adding it

Also, this capability has been integrated into the Directory Server startup
process so that it is now possible to have a config/config-changes.ldif that
will automatically be applied to the config/config.ldif file before it gets
processed by the server.  This makes it easy to make configuration changes with
the server offline without directly altering the configuration file, and can be
used to make changes to the configuration needed for running test cases.

OpenDS Issue Numbers:  622, 623


git-svn-id: https://svn.forgerock.org/opendj/trunk@298 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     

31 Aug, 2006

1 commit

  • f87df99a   Add initial MakeLDIF support for generating entries based on a template. This ... Browse Dir » 
    can be used to either write the generated entries to LDIF, or to import them
directly into the server.  This code is not yet feature-complete, nor is it
100% compatible with the version of MakeLDIF provided with SLAMD, but it is
functional enough for use in a large number of situations.

OpenDS Issue Number:  588


git-svn-id: https://svn.forgerock.org/opendj/trunk@230 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson