Integration Server 10.15 | Added, Removed, Deprecated, or Changed Parameters | Release 10.3
 
Release 10.3
Added Parameters
*watt.net.jsse.server.SSLSessionTimeout Specifies the amount of time in seconds for which Integration Server waits before timing out and removing an SSL session from the SSL cache.
*watt.net.jsse.server.useCipherSuitesOrder Specifies whether the local cipher suites preference should be honored by Integration Server during the SSL/TLS handshake when Integration Server acts as the SSL/TLS server and requires the use of JSSE
*watt.security.kerberos.client.useSPNEGO Specifies whether Integration Server generates a SPNEGO-based Kerberos ticket for all outbound requests that use Kerberos authentication.
*watt.security.max.contentLength Specifies the maximum size limit of the payload for an HTTP request.
*watt.security.max.headerLength Specifies the maximum length of the header for an HTTP request.
*watt.security.max.urlLength Specifies the maximum length of the URL for an HTTP request.
*watt.server.autodeploy.enabled Specifies whether automatic deployment of packages is enabled or disabled for Microservices Runtime.
Note: The automatic package deployment feature is available by default for Microservices Runtime. To use the automatic package deployment feature with Integration Server, your Integration Server must have additional licensing.
*watt.server.autodeploy.interval Specifies the interval, measured in minutes, at which Microservices Runtime executes the autodeploy system task.
Note: The automatic package deployment feature is available by default for Microservices Runtime. To use the automatic package deployment feature with Integration Server, your Integration Server must have additional licensing.
*watt.server.autodeploy.alwaysUseHotDeployment Specifies whether Microservices Runtime always uses hot deployment for automatic deployment of packages.
Note: The automatic package deployment feature is available by default for Microservices Runtime. To use the automatic package deployment feature with Integration Server, your Integration Server must have additional licensing.
*watt.server.checkPath.restorePipelineFromFile Specifies whether Integration Server verifies that the value of the filename input parameter supplied to pub.flow:restorePipelineFromFile service is in the allowedReadPaths parameter of the file access control configuration file (fileAccessControl.cnf).
*watt.server.checkPath.savePipelineToFile Specifies whether Integration Server verifies that the value of filename input parameter supplied for the pub.flow:savePipelineToFile service is in the allowedWritePaths parameter of the file access control configuration file (fileAccessControl.cnf).
*watt.server.coder.responseAsXML Specifies how Integration Server receives the XML response for any REST API request -- in proper XML format or in converted XML format containing IData objects.
*watt.server.jms.trigger.startupFailure.restartTaskRetryCount Specifies the maximum number of retry attempts the trigger restart task makes to start the JMS triggers that fail to start when the JMS connection alias starts up
*watt.server.jms.trigger.startupFailure.restartTaskRetryInterval Specifies the number of seconds that the trigger restart task waits between attempts to restart JMS triggers that failed to start when the JMS connection alias started.
*watt.server.oauth.token.endpoint.auth Specifies whether the token endpoint accepts an existing session or requires credentials for authentication.
*watt.server.publish.maxCSQRedeliveryCount Specifies the maximum redelivery attempts Integration Server makes when publishing a message from the client side queue (CSQ) to the Broker.
*watt.server.SOAP.inbound.CDATA.removeTags Specifies whether Integration Server removes or preserves the CDATA delimiter tags found in an inbound SOAP request.
*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.enterprisegateway.ignoreXForwardedForHeader Specifies whether Integration Server must ignore the 'X-Forwarded-For' request header while processing the rules in Enterprise Gateway. If this property is set to 'true' then Integration Server ignores the 'X-Forwarded-For' request header and considers the proxy server's IP address as the host IP address. If the property is set to 'false' then Integration Server obtains the actual host IP address from the 'X-Forwarded-For' request header. Default value is 'true'.
Removed Parameters
*watt.ssl.iaik.clientAllowUnboundRenegotiate No replacement. This parameter is obsolete. Integration Server uses the Entrust security provider library which has been updated for RFC 5746 to support secure TLS/SSL renegotiation. Secure renegotiation cannot be disabled.
*watt.ssl.iaik.serverAllowUnboundRenegotiate No replacement. This parameter is obsolete. Integration Server uses the Entrust security provider library which has been updated for RFC 5746 to support secure TLS/SSL renegotiation. Secure renegotiation cannot be disabled.
Deprecated Parameters
*watt.server.publish.maxCSQRedeliveryCount No replacement. webMethods Broker is deprecated, resulting in the deprecation of this parameter.
*watt.server.coder.responseAsXML The default value of this parameter is changed to ‘true’.