[Single Invocation]

• wrapper.single_invocation (3.1.2)

  Ensures that only one instance of the Wrapper is running at a given time.

• wrapper.single_invocation.notify (3.5.28) ( Std/Pro )

  Triggers an event and attempts to set focus to the running Java application when a second instance is launched.

• wrapper.single_invocation.notify.focus_window (3.5.28) ( Std/Pro )

  Sets the focus to the top window of the Java application whenever a second instance is launched.

• wrapper.single_invocation.notify.timeout (3.5.28) ( Std/Pro )

  Configures the maximum number of seconds that the Wrapper will wait for a reply from the running instance.

• wrapper.single_invocation.notify.show_splashscreen (3.5.28) ( Std/Pro )

  Shows the splash screen whenever a second instance is launched.

[Share]

• wrapper.share.<n>.target (3.5.0) ( Std/Pro )

  Set the targets on the local machine to which the network resources should get mapped to.

• wrapper.share.<n>.location (3.5.0) ( Std/Pro )

  Set the locations of network resources such as a shared file, directory, or printer.

• wrapper.share.<n>.type (3.5.0) ( Std/Pro )

  Specify the type of network resources to connect to.

• wrapper.share.<n>.account (3.5.0) ( Std/Pro )

  Specify accounts to connect to network resources.

• wrapper.share.<n>.password (3.5.0) ( Std/Pro )

  Specify passwords to connect to network resources.

• wrapper.share.<n>.startup.failure (3.5.0) ( Std/Pro )

  Specify whether to shutdown or continue when failing to mount network resources.

• wrapper.share.<n>.startup.premapped (3.5.0) ( Std/Pro )

  Specify whether to shutdown or continue when network resources could not be mounted because they already exist.

• wrapper.share.<n>.startup.max_retries (3.5.0) ( Std/Pro )

  Define how many times the Wrapper should try to mount network resources.

• wrapper.share.<n>.startup.retry_interval (3.5.0) ( Std/Pro )

  Specify intervals in seconds the Wrapper will wait until it retries to mount network resources.

• wrapper.share.<n>.shutdown.unmap (3.5.0) ( Std/Pro )

  Specify if the Wrapper should disconnect network resources when shutting down.

• wrapper.share.<n>.shutdown.unmap.force (3.5.0) ( Std/Pro )

  Specify whether disconnections should occur even if there are open files or running jobs.

[General/Common]

• wrapper.registry.java_home (3.2.4)

  Specifies a registry key containing the path to the Java home folder.

• wrapper.thread_dump_control_code (3.3.0)

  Specifies the user defined control code that can be sent to the Windows service to initiate a thread dump.

• wrapper.ntservice.load_order_group (3.0.4)

  Specifies the name of the load ordering group of which the service will be a member.

• wrapper.ntservice.dependency.<n> (1.0.0)

  List the names of other services or groups which must be running before this service can be started.

• wrapper.ntservice.process_priority (2.2.7)

  Specifies the priority at which the Wrapper and its JVM will be run.

• wrapper.ntservice.interactive (3.0.0)

  Makes it possible for the service to display a GUI and interact with the desktop.

• wrapper.ntservice.console (3.1.0)

  Causes the Wrapper to allocate and display a console window when running as a Windows service.

• wrapper.ntservice.generate_console (3.3.2)

  Added to force the Wrapper to always create an internal console when running as a Windows service.

• wrapper.ntservice.hide_console (3.0.4)

  Specifies to hide the console when running as a Windows service.

• wrapper.ntservice.preshutdown (3.5.30)

  Enables the service to listen to preshutdown notifications.

• wrapper.ntservice.preshutdown.timeout (3.5.30)

  Configures the maximum number of seconds the service control manager should wait until a service listening to preshutdown notifications will stop.

[Start/Stop]

• wrapper.ntservice.starttype (1.0.0)

  Configures the start mode of the service.

• wrapper.ntservice.pausable (3.2.1, deprecated as of 3.5.0)

  Allows to pause and resume the service from the Services panel or from the command line.

• wrapper.ntservice.pausable.stop_jvm (3.2.1, deprecated as of 3.5.0)

wrapper.ntservice.interactive (3.0.0) Makes it possible for the service to display a GUI and interact with the desktop. wrapper.ntservice.account (3.0.0) Specifies the account to use when running as a Windows service. wrapper.ntservice.account.prompt (3.5.5) Asks the user to input the domain, account name and password in order to install the Wrapper as a Windows service. wrapper.ntservice.password (3.0.0) Sets the password for a specific user account. wrapper.ntservice.password.prompt (3.2.0) Asks the user to input a password when installing the Wrapper as a service. wrapper.ntservice.password.prompt.mask (3.2.0) Prevents your password to be displayed in the console. wrapper.ignore_user_logoffs (3.3.1) Controls whether or not the Wrapper will respond to Windows LogOff events when running in console mode.

[View/Display]

• wrapper.ntservice.name (1.0.0)

  Configures the service name used in error messages, events, etc.

• wrapper.ntservice.displayname (1.0.0)

  Sets the display name used in the Services panel.

• wrapper.ntservice.description (2.2.5)

  Sets the description used in the Services panel.

• wrapper.splashscreen.mode (3.3.7) ( Std/Pro )

  Configures the moment to display the splash screen when running "wrapperW.exe".

[Recovery]

• wrapper.ntservice.recovery.reset (3.5.5) ( Std/Pro )

  Configures the time in seconds, without any errors, after which the service control manager will reset the failure count to 0.

• wrapper.ntservice.recovery.command (3.5.5) ( Std/Pro )

  Configures a command to be executed in a response to a failure.

• wrapper.ntservice.recovery.reboot_msg (3.5.5) ( Std/Pro )

  Specifies a message to be logged in the Event Viewer when the system reboots due to a service failure.

• wrapper.ntservice.recovery.<n>.failure (3.5.5) ( Std/Pro )

  Configure the actions to take place when the Wrapper service crashes or exits <n> times.

• wrapper.ntservice.recovery.<n>.delay (3.5.5) ( Std/Pro )

  Configure the maximum number of seconds the service control manager should wait until it actually performs the specified actions.