org.forgerock / org.forgerock.opendj

05 Feb, 2008

1 commit

  • 18a5f38d   Fix for issue 2902 (stop-ds -R restarts the server with client tool JVM) ... Browse Dir » 
    When the java properties are set to not overwrite the environment variables (which is the default behavior) when we call start-ds from the stop-ds scripts, OPENDS_JAVA_ARGS is already set with the arguments for the stop (client arguments).  The fix consists basically on resetting the environment variables to those we had before calling stop-ds before calling start-ds.


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

03 Jan, 2008

1 commit

21 Dec, 2007

2 commits

17 Dec, 2007

1 commit

  • b5ad1173   2730: New - The setup command should perform some basic memory tuning ... Browse Dir » 
    Note: this issue is not fully covered by the proposed modifications but
all that is missing in order to fix it is to figure out which are the
default memory values that we want to propose in the setup.

2620: Server should be started as server JRE and clients should be
started as client JREs

The proposed solution goes beyond fixing the two issues and proposes a
manner for the user to set specific java arguments (and use a specific
JVM) for every command-line.

Today the user can specify the JVM to be used using the OPENDS_JAVA_HOME
environment variable and the java arguments by using the
OPENDS_JAVA_ARGS environment variable.  In the case of the JVM this
covers most of the use cases (in general we will use the same JVM for
all the command-lines).  However this is quite limiting in the case of
the java arguments we pass.  For instance in general we want to run the
server (start-ds command-line) using the server mode of the JVM but
other command-lines using the -client mode of the JVM.  In the same
manner we might want to have a bigger heap when running the server than
when we are running a "lightweight" utility as dsconfig.

The proposed solution is to have a properties file called
java.properties where the user specifies the different JVM and java
arguments to be used for every command-line.  Once the user has edited
this properties file, (s)he must run a command-line called
dsjavaproperties that will update all the scripts to use the arguments
specified in that properties file.

NOTE: there are a number of command-lines (import-ldif, export-ldif,
backup, restore) where the user will be able to specify different java
arguments (and different JVM) to use depending on whether the
command-line is run in online or offline modes.  You can see the
comments on java.properties to get more information about this and in
general about the different properties that can be set.

The modification in the setup basically try to check if the JVM that is
being used to run the setup (the one that will be used by default)
supports the -client and -server options.  Depending on the results of
these checks the setup will update the java.properties file and then run
dsjavaproperties to update the scripts. 


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

28 Sep, 2007

1 commit

  • f031cee6   Fix for issue 2035 (Use OpenDS specific environment variables to determine the JVM to be used.) ... Browse Dir » 
    Use two environment variables to know which is the JVM to be used by the scripts: OPENDS_JAVA_BIN and OPENDS_JAVA_HOME.

When the setup creates the file lib/set-java-home it writes the contents of OPENDS_JAVA_HOME to it (instead of JAVA_HOME which was the previous behavior).

Before these changes, the scripts used to look for JAVA_BIN, then JAVA_HOME and finally for the contents of the set-java-home file.  The problem with this approach is that if the user required to specify JAVA_HOME or JAVA_BIN to an unsupported version of the JDK (because some other program in the machine had this requirement) the scripts of OpenDS could not run.  Now the checks that we do to figure out the JVM are done in the following order:
1. Check if OPENDS_JAVA_BIN is defined in the environment.
2. Check if OPENDS_JAVA_HOME is defined in the environment.
3. Check if OPENDS_JAVA_HOME is defined in the lib/set-java-home file.
4. Check if JAVA_BIN is defined in the environment.
5. Check if JAVA_HOME is defined in the environment.
6. Check if we can figure out the java installation by executing "type java" (in UNIX environments).

If any of the above checks is positive, we will try to use the JVM found.

Extras: the uninstall script on UNIX now checks that we are using a JDK compatible with 1.5 and displays a user friendly message if it does not.




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

25 Sep, 2007

1 commit

13 Sep, 2007

1 commit

  • 6b9e0a2b   Introduces a utility 'manage-tasks' for monitoring and some management of tasks … ... Browse Dir » 
    …called 'manage-tasks'. It can be used in either one-time or menu-driven execution mode to print a summary of task information, print verbose information about a particular task, or cancel a running or pending task.

When starting the tool, 'manage-tasks' requires a connection to the directory to interact with the backend and prompts for information (unless given the -n/--no-prompt option) like 'dsconfig'


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

12 Sep, 2007

1 commit

  • 0a6de46c   Fix for issues: ... Browse Dir » 
    1335: define, document, review CLI to register a server in a synch
1336: CLI implementation to register a server in a synchronization
1878: provide a CLI to initialize a replication topology from a gi
2201: ads-trustore missing when not configuring replication with t
2250: Setup and dsreplication utilities should configure schema sy


Extra: do not show dc=replicationchanges suffix in the replication panel of the setup, nor propose it to replicate.
fix some bugs related to duplicate error messages displayed in dsreplication interactive mode.



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

10 Sep, 2007

1 commit

06 Sep, 2007

1 commit

05 Sep, 2007

2 commits

29 Aug, 2007

1 commit

  • c272923e   Update the CreateRCScript tool so that it provides the ability to specify the ... Browse Dir » 
    user that the server should run as (invoked via "su"), and also lets the user
specify the JAVA_HOME and JAVA_ARGS settings that should be used.

This also updates the start-ds and stop-ds commands to support a --quiet
argument, which causes them to not generate any output.  The generated RC
script uses this option, since server startup output shouldn't be generated at
system boot time.


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

27 Aug, 2007

1 commit

  • f6f75dc2   This adds the numSubordinates and hasSubordinates operational attribute support in OpenDS. ... Browse Dir » 
    - Implemented as virtual attributes
   - They are enabled by default
   - numSubordinates and hasSubordinates methods added to the backend API and implemented for all existing backends
   - JE implementation uses the id2children index to keep count of the number of subordinates for each entry.
   - The behavior of exceeding the index-entry-limit (ALL-IDs) has changed to store a 8 byte entry ID set count with the most significant bit 
set to 1 instead of a 0 byte array to signify the index-entry-limit has been exceeded. The previous format is still compatible but all requests 
for numSubordinates will return undefined (-1).
   - The DBTest tool is also included in this fix. This can be used to list root containers, entry containers, database containers, index 
status, as well as dumping a database with or without decoding the data. 

Fix for issues 43 and 72


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

24 Aug, 2007

2 commits

17 Aug, 2007

1 commit

  • ceb3ab47   The following modifications have the following goals: ... Browse Dir » 
    1. Provide a fix for the CLI part of issue 1894 (consider replication in uninstall).  The command line now proposes to remove references in remote servers of the server that is being uninstalled.

2. Add options to specify to uninstall only some parts of the server as appears in http://bde.central.sun.com/projects/opendsw/cmdline/commandmatrix.html.

3. Fix some bugs in the messages.

4. The fix of 1894 includes some code to display certificates to the user so that they can be viewed and accepted interactively.

5. Separate the uninstall command-line into two different command lines (uninstall-gui and uninstall)  as appears in http://bde.central.sun.com/projects/opendsw/cmdline/commandmatrix.html.


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

07 Aug, 2007

1 commit

  • 2f1a0654   The following modifications have the following goals: ... Browse Dir » 
    1. Provide a fix for the GUI part of issue 1894 (consider replication in uninstall).  Basically the graphical uninstall checks whether there is an ADS defined and if the server is configured for replication and asks the users whether (s)he wants to remove the references to the server that is being uninstalled.

2. Fix some minor issues that appear in the merged version of the installer and upgrader.

3. Update the build so that statuspanel.jar disappears.  The idea is to minimize the number of jars that we have.  This is a requirement coming from customers and approved by Neil in a conversation we had a while ago.

4. Minimize the number of classes that go to quicksetup.jar so that its size is the minimal possible and we reduce the download time when launching the WebStart based tools.  This has been done by moving the uninstaller tool to OpenDS.jar (with the status tools). 


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

25 Jul, 2007

1 commit

23 Jul, 2007

2 commits

18 Jul, 2007

1 commit

  • e080cfae   Fix for issue 1603 (quickInstall fails to register service on vista) ... Browse Dir » 
    With the new user access control of Vista, even if we are administrators we are not allowed to do certain operations (such as writing in the service registry) in some circumstances.  For instance if we launch net start <service_name> from a normal command prompt this will fail systematically.  In order to be able to execute these "privileged" operations we have different alternatives:

Execute the binary that will do the operations using the "Run as Administrator" option in Vista (or launching them from a command prompt that has been started using that same option).
Add a manifest to the binary informing that the binary requires administrator privileges.

The first alternative is one of the workarounds for the bug, however it does not apply to the case of the Java Web Start Installer.

The second alternative is in what consists the bug fix.  A new binary has been created.  This binary has a manifest informing that it requires administrator privileges.  This binary will be used in Vista as a wrapper to call operations that require administrator privileges (modifying the registry in windows-services.bat command line and calling "net start" and "net stop").  

If the user is running the setup, the status-panel using the "Run as Administrator" option or is using the command lines from a command prompt launched with that option the behavior in Vista does not change with the behavior in previous versions of Windows.

If the UAC is enabled and the user is not using the "Run as Administrator" options, (s)he will be prompted for confirmation each time the registry is modified and the server is started or stopped as a service.  The wrapper is called on any of the individual operations.  An alternative would be to call the wrapper when we launch the setup or the status-panel but this generates some issues:
1. This does not work (directly) with the Java Web Start installer.
2. This would force users that are not administrators to provide administrator credentials even to install/run an OpenDS that does not require to do privileged operations (an OpenDS that does not run as a service).


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

11 Jul, 2007

1 commit

27 Jun, 2007

2 commits

  • 6fc3930f   Add a new extended operation that can be used to interact with password policy ... Browse Dir » 
    state information for a user, including getting and setting various state
variables (even those marked NO-USER-MODIFICATION, although these are typically
intended for testing purposes only).  Users will be required to have the
password-reset privilege in order to be able to use this extended operation,
and access control will also come into play.

Also, include a manage-account tool that can be used to interact with this
extended operation.  It supports a subset of the capabilities made available in
the extended operation (e.g., it only allows one operation per use, whereas the
extended operation allows you to include multiple operations), and some of the
features intended for testing purposes are marked hidden so that they aren't
readily apparent to end users.

Finally, fix a bug in which it was not possible for users to authenticate if
their account had the pwdReset flag and last login time tracking was enabled.

OpenDS Issue Numbers:  292, 579, 1782, 1845


git-svn-id: https://svn.forgerock.org/opendj/trunk@2201 41b1ffd8-f28e-4786-ab96-9950f0a78031
    neil_a_wilson
     
  • 711d234f   rename dsservice to dsframework ... Browse Dir » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2192 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     

22 Jun, 2007

2 commits

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