Fix windows batch if instance.loc is missing - OPENDJ-1069

Fix for OPENDJ-132: upgrade utility does not accept relative path. Contribution from German Parente (thanks)

Fix for OPENDJ-222 : Renamed environment variables to OPENDJ_... Updated scripts so that if OPENDJ_JAVA_HOME and OPENDJ_JAVA_ARGS are not defined, we look at the legacy OPENDS_... ones.

Minimize Historical Data (dsreplication/client side). The purge historical can be executed on the local server even when it is stopped. This is matches the functionality provided by utilities such import-ldif, backup, etc.

Fixed typo in param passing in Windows bat files

svn merge -r5333:5417 https://opends.dev.java.net/svn/opends/branches/b2.0

fix for issue #3498 - stop-ds.bat doesn't work anymore if not launched from server root (OpenDS1.1.0) windows 'cd' cmd should be used with the '/d' modifier

These changes are separating the current delivery into an "Install Layout" (the binaries) and an "Instance Layout" (the user data).

Fix for issue 2969 (In some cases the arguments set for offline operations (import-ldif, export-ldif) are the ones of the online mode) The problem comes because when we are dealing with scripts that can have both online and off-line modes we call _script-util to know whether we must run the script in online or off-line modes. This makes the environments variables to be set, so when we call the second time _script-util (to set the environment for the off-line mode) nothing is changed if the user specified not to overwrite the environment variables. The fix consists on resetting the environment variables to its original state before calling _script-util for the second time.

Updated the copyright statement to reflect that Sun owns the full copyright on the project files.

2730: New - The setup command should perform some basic memory tuning 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.