425N/A# The contents of this file are subject to the terms of the
425N/A# Common Development and Distribution License, Version 1.0 only
425N/A# (the "License"). You may not use this file except in compliance
425N/A# See the License for the specific language governing permissions
425N/A# and limitations under the License.
425N/A# When distributing Covered Code, include this CDDL HEADER in each
425N/A# If applicable, add the following below this CDDL HEADER, with the
425N/A# fields enclosed by brackets "[]" replaced with your own identifying
425N/A# Portions Copyright [yyyy] [name of copyright owner]
425N/A# Copyright 2008-2010 Sun Microsystems, Inc.
425N/A# Portions Copyright 2011 ForgeRock AS
1244N/A# This file contains the java properties that the different command lines will
425N/A# use when launched. You can specify the location of the java binaries to be
425N/A# used and the java arguments to be passed to the command line.
844N/A# For instance you can specify to use the -server argument for the start-ds
844N/A# command with an initial heap size of 256 Mb by setting
1258N/A# (the example assumes that the Java virtual machine supports those options).
2899N/A# To set the java virtual machine to be used for a given command-line you must
2899N/A# set the property <command-line-name>.java-home and to specify java arguments
425N/A# you must set the property <command-line-name>.java-args.
425N/A# There are certain command-lines (import-ldif, export-ldif, backup, restore)
425N/A# that can work on two modes: online and offline. When they run in online mode
425N/A# (the server is running and the user specifies LDAP parameters to launch the
425N/A# operation) the operation is not actually performed in the Java Virtual Machine
425N/A# of the command-line but on the server side. This is why when launching these
425N/A# command-lines on online-mode it is preferred to use the -client argument for
425N/A# the java virtual machine (and even limit the maximum size of the heap).
3639N/A# However when these command-lines are launched in offline mode it is
3639N/A# recommended to use the -server argument to launch the command-line.
3639N/A# This is the reason why you can specify different java properties for both
3639N/A# IMPORTANT NOTE: Once you have modified this file and set the java properties
3639N/A# that you want the command-lines to use you must run the command-line
3639N/A# Specify to overwrite the content of the environment variable OPENDJ_JAVA_HOME
425N/A# (
i.e. the contents of this properties file for the java home will be analyzed
1475N/A# before checking whether OPENDJ_JAVA_HOME is specified in the environment):
1475N/A# overwrite-env-java-home=true
3477N/A# Specify to overwrite the content of the environment variable OPENDJ_JAVA_ARGS
3477N/A# (
i.e. the contents of this properties file for the java args will be analyzed
425N/A# before checking whether OPENDJ_JAVA_ARGS is specified in the environment):
425N/A# overwrite-env-java-args=true
425N/A# Specify to use a particular Java Virtual Machine for the offline import:
425N/A# Specify to use -client argument when running dsconfig:
# Specify to use -server argument when running import-ldif on server mode:
# Specify to use the java home for all the command-lines that have not
# an associated property defined:
# Specify to use the -client argument for all the command-lines that have not
# an associated property defined: