The wrapper.share.<n>.shutdown.* properties specify how the Wrapper will handle the mounted shares during the shutdown of the Wrapper (not the JVM). The shares will only be unmounted at this time. During a JVM restart for instance, they won't be un- and remounted.

Furthermore, the Wrapper will not try to unmount any Network Drive which hasn't been mounted by the current Wrapper process.

• wrapper.share.<n>.shutdown.unmap
• wrapper.share.<n>.shutdown.force
• Putting it all together

<n> component:

The "<n>" component of the property name is an integer number counting up from "1". By default, there can be no missing numbers. The wrapper.ignore_sequence_gaps property can optionally be set to allow gaps in the sequence.

wrapper.share.<n>.shutdown.unmap

Compatibility : 3.5.0 Editions : Platforms : Specifies if the Wrapper should disconnect the Network Drive at shutdown of the Wrapper. If the drive already existed when the Wrapper started, the property will be ignored and the drive will be left mounted. The default value is "FALSE", which means that the Wrapper will NOT disconnect the drive. Example: wrapper.share.1.shutdown.unmap=FALSE NOTE The default value (FALSE) was chosen for cases where multiple services use the same share. If this share was unmounted when stopping the first service, it would make it unavailable for other services. However, in situations where you know that a share is only used by one service, it is usually better to change the value to TRUE to automatically revert to the state before the Wrapper started.

wrapper.share.<n>.shutdown.unmap.force

Compatibility : 3.5.0 Editions : Platforms : This property specifies whether the disconnection should occur if there are open files or jobs on the connection. If this parameter is FALSE, the function fails if there are open files or jobs and the Network Drive will persist. The default value is "FALSE". Example: wrapper.share.1.shutdown.unmap.force=FALSE

The example of "share" properties would be helpful.