[Single Invocation]

• wrapper.single_invocation (3.1.2)

  Makes it possible to control/allow a given application to have a single or multiple invocations at the same time.

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

  Notify for any attempt made to launch a second instance. This will trigger an event and attempt to set focus to the Java application.

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

  Make it possible to set the focus to the top window of the Java application

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

  Configures the number of seconds allowed for the Wrapper to take action in response to a second invocation.

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

  Make it possible to hide or show the splashcreen when a second instance is launched in single invocation mode.

[Share]

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

  Sets the target on the local machine to which specified resources whould get mapped to.

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

  Sets the location of resource such as the Windows Share or Network Printer in UNC format.

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

  Specifies the type of network resource to connect to.

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

  If users want to connect to a Network Resource other than the default user name or account.

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

  This property sets the password affiliated to an assigned account.

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

  This property defines the behaviour of the Wrapper if any general error occured.

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

  This property specifies what the Wrapper will do if a share couldn't be mounted because the Network Resource already existed.

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

  This property defines how many times the Wrapper should try to mount a Network Drive.

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

  Specifies the interval in seconds the Wrapper will wait until it retries to mount a Network Drive.

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

  Specifies if the Wrapper should disconnect the Network Drive at shutdown of the Wrapper.

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

  Specifies whether the disconnection should occur if there are open files or jobs on the connection.

[General/Common]

• wrapper.registry.java_home (3.2.4)

  Configures the JVM in order to be launched through the Windows registry.

• wrapper.thread_dump_control_code (3.3.0)

  Thread dumps can be configured to take place based on specific codes.

• 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)

  Names of any 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 at, when run as a Windows Service or as a console application.

• wrapper.ntservice.interactive (3.0.0)

  Makes it possible for the service to display a GUI and have access to the desktop when run as a service.

• wrapper.ntservice.console (3.1.0)

  Causes the Wrapper to allocate and display a console window when running as a Windows Service or with the consoleless version of the Wrapper binary.

• wrapper.ntservice.generate_console (3.3.2)

  Added to force the Wrapper to always create an internal console when running as a Windows Service or with the consoleless version of the Wrapper binary.

• wrapper.ntservice.hide_console (3.0.4)

  This property is ignored unless the Wrapper is being run as a Windows Service.

• wrapper.ntservice.preshutdown (3.5.30)

  Specifies that the service will accept PRESHUTDOWN notifications.

• wrapper.ntservice.preshutdown.timeout (3.5.30)

  Tells the service control manager how long to wait until a service listening to PRESHUTDOWN notifications will stop.

[Start/Stop]

• wrapper.ntservice.starttype (1.0.0)

  Configuration of properties for ntservice.

• wrapper.ntservice.pausable (3.2.1 (Deprecated as of 3.5.0))

  This property makes it possible to pause and resume the service from the Services Control Panel as well as from the command line.

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

Reference: Account

wrapper.ntservice.interactive (3.0.0) Makes it possible for the service to display a GUI and have access to the desktop when run as a service. wrapper.ntservice.account (3.0.0) Configures the account to use when running the service. wrapper.ntservice.account.prompt (3.5.5) The Wrapper will ask the user to input the domain, account name and password in order to install the Wrapper as Windows Service. wrapper.ntservice.password (3.0.0) Sets up the password for a specific account user. wrapper.ntservice.password.prompt (3.2.0) This property will cause the Wrapper to ignore any value specified in the password set up for an account user. wrapper.ntservice.password.prompt.mask (3.2.0) This property is set by default and only used in Windows, it prevents your password to be displayed in the console. wrapper.ignore_user_logoffs (3.3.1) Controls if the Wrapper should respond to events when a session is terminated.

[View/Display]

• wrapper.ntservice.name (1.0.0)

  Configures the Service Name on Windows when an application is installed.

• wrapper.ntservice.displayname (1.0.0)

  This property is only used on Windows platforms, displaying the service name when an application is installed.

• wrapper.ntservice.description (2.2.5)

  This property is only used on Windows platforms, displaying the service description when an application is installed.

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

  Customizes the splashscreen used only for the consoleless version of the Wrapper binary.

[Recovery]

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

  Configures the time in seconds, without any errors, after which the Service Manager will reset this counter back to 0 (zero).

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

  This can be used to do things like perform cleanup or send external notification.

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

  This property is used to define the text of the message generated with information about Why the system was rebooted?

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

  This property sets the failure action which should happen if the Wrapper service crashes or exits with an error.

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

  Configures the time the Service Control Manager should wait until the next specified action actually starts.