watt.core.schema.generateObsoleteDocumentTypeNames Specifies whether Integration Server uses the naming convention that existed prior to version 8.2 when generating document types for complex types referenced from a global element declaration.

watt.core.transientStore.logExceptions Specifies whether Integration Server logs exceptions thrown by the transient store that might cause the consumer thread to terminate. This can aid in diagnosing problems with an internal store used by the resubmission process.

watt.frag.keep.original.servicename Specifies whether Integration Server retains the original service name for input fields while fragging or compiling a Java service.

watt.net.clientKeepaliveAgingLimit Specifies how long a socket in a client connection pool is kept alive, measured in seconds.

watt.net.clientKeepaliveUsageLimit Specifies the maximum number of usages for a socket in a client connection pool.

watt.server.audit.file.fieldDelimiter Specifies the character sequence to use to delimit fields within a log record in a file-based audit log

watt.server.audit.file.recordDelimiter Specifies the character sequence to use to delimit records in a file-based audit log.

watt.server.audit.stdout.fieldDelimiter Specifies the character string to delimit audit log fields within a log entry when the audit log is written to the console (STDOUT).

watt.server.audit.stdout.recordDelimiter Specifies the character string to delimit the audit log records when the audit logger is written to the console (STDOUT).

watt.server.package.maxSizeMB Specifies the maximum expanded size of a package that can be installed, measured in megabytes.

watt.server.serviceMonitor.queryOnServerId Specifies monitoring capabilities for the entire stateful cluster and not just for a single instance of the cluster.

watt.server.SOAP.retainUndeclaredNamespace Specifies whether Integration Server retains namespaces from an xsd:any element when decoding a SOAP request or SOAP response.

watt.server.search.fast Specifies whether Integration Server must process the value assigned to the pipeline variable while loading a flow service thereby enhancing the search operation and displaying the search results much faster.

watt.server.package.pre82WSD.loadExternalResources No replacement. The web services implementation that handles web services that run in pre-8.2 compatibility mode is deprecated, specifically the implementation introduced in Integration Server version 7.1. As a result, this parameter is deprecated.

watt.server.setResponse.pre82Mode No replacement. The web services implementation that handles web services that run in pre-8.2 compatibility mode is deprecated, specifically the implementation introduced in Integration Server version 7.1. As a result, this parameter is deprecated.

watt.server.soap.convertPlainTextHTTPResponseIntoSOAPFault No replacement. The web services implementation that handles web services that run in pre-8.2 compatibility mode is deprecated, specifically the implementation introduced in Integration Server version 7.1. As a result, this parameter is deprecated.

watt.server.SOAP.pre82WSD.ignoreVersionMismatch No replacement. The web services implementation that handles web services that run in pre-8.2 compatibility mode is deprecated, specifically the implementation introduced in Integration Server version 7.1. As a result, this parameter is deprecated.

watt.server.ws.responseTNS.from.request No replacement. The web services implementation that handles web services that run in pre-8.2 compatibility mode is deprecated, specifically the implementation introduced in Integration Server version 7.1. As a result, this parameter is deprecated.

watt.server.cors.allowedOrigins To make it easier to specify a long list of allowed URIs, Integration Server now allows specifying a file as the value for this parameter.

watt.server.cors.exposedHeaders This parameter is no longer case-sensitive.

watt.server.netEncoding When the pub.client:http service submits a password digest for authentication (that is, the auth/type field is set to Digest) and the HTTP server response includes the header field “Content-Type” but does not contain the charset parameter, uses the value of the watt.server.netEncoding server configuration parameter as the default character set.

watt.server.SOAP.ignoreMissingResponseHeader This parameter now ignores missing required headers for returned SOAP faults.