Compatibility :3.5.28
Editions :Professional EditionStandard EditionCommunity Edition
Platforms :WindowsMac OSX (Not Supported)Linux (Not Supported)IBM AIX (Not Supported)FreeBSD (Not Supported)HP-UX (Not Supported)Solaris (Not Supported)IBM z/OS (Not Supported)IBM z/Linux (Not Supported)

Used to tell the Wrapper whether to register to the Windows event log by creating an identifier (also known as event source). When this property is set to FALSE, any existing identifier will be deleted. The default value is TRUE.



Creating an event source implies adding a key to the registry. The name of the key can be specified with the wrapper.syslog.ident property.

Starting with Windows Vista or Windows Server 2008, the creation of the registry key requires administrative credentials. When running on a lower permission, the Wrapper will silently ignore this property and start without changing the registration of the application.

Event logging will be automatically disabled if there is no identifier for the current application or service. Existing logs will remain in the Event Viewer but their source will not be authenticated and an error message will be displayed.

Example of error message appearing when the source could not be authenticated:
The description for Event ID 100 from source testwrapper cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

To avoid the above message, it is a normal practice to keep the event source in the registry after stopping or uninstalling the application if the past logs still need to be consulted.

To manually register or unregister to the event log, use the --setup or the --teardown options, or their respective Batch files.

Reference: Syslog/Event Log