The Campaign | unicaACListener properties specify logging levels, some access privileges, language encodings, number of operating system threads, and the protocol, host, and port of the
Campaign listener. These properties must be set only once per instance of
Campaign; they do not need to be set for every partition.
The enableWindowsImpersonation property specifies whether
Windows™ impersonation is enabled in
Campaign.
Set the value to TRUE if you are using
Windows™ impersonation. You must configure
Windows™ impersonation separately if you want to leverage the Windows-level security permissions for file access.
The Campaign > unicaACListener > enableWindowsEventLogging property controls logging to the
Windows™ event log. Set this property to
TRUE to log to the
Windows™ event log.
The serverHost property specifies the name or IP address of the machine where the
Campaign listener is installed. If the
Campaign listener is not installed on the same machine where
IBM® Unica Marketing is installed, change the value to the machine name or IP address of the machine where the
Campaign listener is installed.
The logMaxBackupIndex property specifies how many backup files can exist before the oldest one is deleted. If you set this property to
0 (zero),
Campaign does not create any backup files and the log file stops logging when it reaches the size you specified in the
logMaxFileSize property.
If you specify a number (N) for this property, when the log file (
File) reaches the size you specified in the
logMaxFileSize property,
Campaign renames the existing backup files (
File.1 ... File.N-1) to
File.2 ... File.N , renames the current log file
File.1, closes it, and and starts a new log file named
File.
1 (creates one backup file)
The logStringEncoding property controls the encoding used for all log files. This value must match the encoding used on the operating system. For multi-locale environments, UTF-8 is the preferred setting.
The systemStringEncoding property indicates which encodings
Campaign uses to interpret values received from and sent to the operating system, such as file system paths and filenames. In most cases, you can set this value to
native. For multi-locale environments, use
UTF-8.
See Character encodings in Campaign in the
Campaign Administrator's Guide.
The Campaign > unicaACListener > loggingLevels property controls the amount of detail written to the log file.
The Campaign > unicaACListener > maxReuseThreads property sets the number of operating system threads cached by the
Campaign listener process (
unica_aclsnr) for reuse.
0 (zero), which disables the cache
The logMaxFileSize property specifies the maximum size, in bytes, that the log file can reach before rolling into the backup file.
The windowsEventLoggingLevels property controls the amount of detail written to the
Windows™ event log file based on severity.
The ALL level includes trace messages intended for diagnostic purposes.
The serverPort property specifies the port where the
Campaign listener is installed.
The useSSL property specifies whether to use Secure Sockets Layer for communications between the
Campaign listener and the
Campaign web application.
The serverPort2 property, in conjunction with the
useSSLForPort2 property, also in this category, enables you to specify the use of SSL for communication between the
Campaign listener and flowchart processes, separately from the communication between the
Campaign web application and listener, which is specified by the
serverPort and
useSSL properties in this category.
All communication between Campaign components, (between the web application and listener and between the listener and server) use the mode specified by the
useSSL property under any of the following conditions.
|
serverPort2 is set to a non- 0 value different from the value of serverPort, and
|
The Campaign web application always uses the communication mode specified by
useSSL when communicating to the listener.
Use the keepalive property to specify, in seconds, the frequency with which the
Campaign web application server sends keep alive messages on otherwise-inactive socket connections to the
Campaign listener.
Using the keepalive configuration parameter enables socket connections to remain open through extended periods of application inactivity in environments configured to close inactive connections between the web application and the listener (for example, a firewall).
0, which disables the keepalive feature
Copyright IBM Corporation 2013. All Rights Reserved.
|