This is an internal parameter. Do not modify.

Specifies how often, in milliseconds, Integration Server checks for the availability of the My webMethods Server database, if the database is unavailable at Integration Server startup. While the database is unavailable, group information about users that are managed by Central User Management is unavailable. As a result, users in those groups do not have the access rights granted by their associated ACLs. While the My webMethods Server database is unavailable, the Security > Access Control List screen displays the affected groups with the suffix @--@, for example FinanceGroup@--@. When the My webMethods Server database becomes available, the groups regain their access rights and Integration Server removes the @--@ suffix. The default setting is 10,000 milliseconds (10 seconds).

Restricts the use of specified directives to specified ports. For information on directives, see Controlling the Use of Directives). The syntax for this property is:

port-string is a comma-delimited list of port numbers such as "5555,6666".

Suppose you want to allow all ports to use the default directive, but you want specific ports to use the other directives, as described below:

To obtain the behavior described above, you would specify the following:

Specifies the URL for establishing a connection to API Portal and publishing a REST API descriptor. This parameter derives the API Portal URL from the following:

Specifies the character set used by the audit logging database. The default is UTF-8. The value for this property must be a standard Internet Assigned Numbers Authority (IANA)-assigned character set name, as defined in the IANA Character Sets specification.

Specifies how dates are displayed when you view the service, error, session, guaranteed delivery, and security logs from the Integration Server Administrator. When this property is set to false, time stamps are shown as GMT/UTC. When this property is set to true (the default), time stamps are shown in the local time zone of the Integration Server, and in the format specified by watt.server.dateStampFmt.

Specifies a custom document ID value to identify documents in a standard way and to provide uniform business context in the logging display. Some documents are logged by webMethods Broker through WmLogUtil to the document database, and some are logged by various components within the Integration Server, for example, if a service fails, or if the number of retries in a trigger are exceeded. As a result, when viewing the Document Monitor, some documents are logged with a numeric document ID, and some are logged with lengthy hexadecimal strings as the document ID. The custom document ID value that you specify will be used to create the document logging ID. This value is used in place of the BrokerEvent.getEventId() value (the original document ID behavior). The value must be in the form of a Broker unicode string, and values in excess of 128 characters will be truncated. If this extended setting is missing, the original document ID behavior applies. If this extended setting is present but undefined (null), the _env.uuid value is used if present; if no _env.uuid value is defined, the original document ID behavior applies. For more information about document logging, see Administering webMethods Broker.

Specifies the loggers that can enter into fail-fast mode when fail-fast mode is enabled for the ISCoreAudit functional alias.

If you want to identify the specific audit loggers that can enter fail-fast mode, use the watt.server.audit.failFastLoggers to specify a comma-separated list of the loggers that can enter into fail-fast mode. For example, if you want the Service Logger and Session Logger to be able to enter into fail-fast mode, set the property as follows:

You must specify the word "Logger" as part of the logger name. The property is case-sensitive. You must specify the logger name as it appears on the Settings > Logging page of Integration Server Administrator. Do not include a space before or after the comma that separates logger names.

Only synchronous loggers can enter fail-fast mode. Integration Server ignores any asynchronous loggers specified in the watt.server.audit.failFastLoggers property.

The default for watt.server.audit.failFastLoggers is empty. That is, the default is that all synchronous audit loggers that use a database destination will have fail-fast capability when the ISCoreAudit functional specifies Yes for the Fail-Fast Mode Enabled option.

Specifies the directory that contains the audit log files. You can specify the full-path name, or a relative path in relation to the Integration Server. The directory must exist on the server. The default value is logs, which indicates the Integration Server_directory \instances\instance_name\logs directory. If an invalid value is specified, Integration Server uses the default value and writes an error to the server log during startup.

Note that watt.server.audit.logDir does not affect audit loggers that write to a database.

Specifies the number of audit log files, including the current log file for the audit logger, that Integration Server keeps on the file system for an audit logger that writes to a file. When Integration Server reaches the limit for the number of log files for the audit logger, each time Integration Server rotates the audit log, Integration Server deletes the oldest archived audit log file. If you set watt.server.audit.log.filesToKeep to 1, Integration Server keeps the current audit log file and no previous audit log files for each file-system based audit logger. That is, when Integration Server rotates the audit log for a logger, Integration Server does not create an archive file for the previous audit log. If you set watt.server.audit.logFilesToKeep to 0, or any value less than 1, Integration Server keeps an unlimited number of audit log files.

The default value of watt.server.log.filesToKeep is 0, indicating that there is no limit to the number of audit log files that Integration Server maintains for audit loggers that write to a file.

The watt.server.audit.logFilesToKeep parameter affects only the audit loggers configured to write to a file. The parameter does not affect audit loggers configured to write to a database nor does it affect the FailedAuditLog.

If you reduce the number of logs that Integration Server keeps for file-based audit logs and then restart Integration Server, the existing audit logs will not be pruned until Integration Server writes to the audit log. For example, if the error logger writes to a file and you reduce the number of log files to keep from 10 to 6, Integration Server does not delete the 4 oldest error audit log files immediately after start up. Integration Server deletes the 4 oldest error audit logs after the error logger writes to the error audit log.

Specifies the file size at which Integration Server rolls over the audit log for a logger that writes to a file. Set this property to N[KB|MB|GB], where N is any valid integer. The minimum size at which Integration Server rotates an audit log is 33KB. If you use KB as the unit of measure, you must set N to a value greater than or equal to 33. If you do not specify a unit of measure, Integration Server treats the supplied N value as bytes. In this case, N must be greater than or equal to 32768 to take effect. Do not include any spaces between the integer and the unit of measure.

There is no default value for this parameter. That is, by default, the parameter has no value. If no value is specified for watt.server.audit.logRotateSize, Integration Server rotates the audit logs at midnight only.

If an invalid value is specified, Integration Server proceeds as if no value was specified for the parameter. If you set the value using the Extended Settings page in Integration Server Administrator, validation prevents an invalid value from being saved.

The watt.server.audit.logRotateSize parameter affects only the audit loggers configured to write to a file. The parameter does not affect audit loggers configured to write to a database.

For more information about audit logging, see the webMethods Audit Logging Guide.

Specifies the name of the database schema that Integration Server should use while requesting metadata for the audit logging database. There is no default. If watt.server.audit.schemaName is not set, Integration Server does not retrieve database metadata and assumes the lengths of the WMSERVICECUSTOMFLDS.STRINGVALUE and WMSERVICEACTIVITYLOG.FULLMESSAGE columns are 512 and 1024, respectively.

Specifies the minimum number of sessions in the Universal Messaging session pool. Integration Server maintains a separate session pool for each Universal Messaging connection alias used by an audit logger. The value of this parameter must be an integer value greater than 0 and less than or equal to the value of watt.server.audit.um.sessionPool.max. The default value is 2.

If you specify an invalid value, Integration Server logs a warning message at start up and then uses the default value at runtime. However, Integration Server does not persist the default value over the invalid value you specified.

Specifies the maximum number of sessions in the Universal Messaging session pool. Integration Server maintains a separate session pool for Universal Messaging connection alias used by an audit logger. The value of this parameter must be an integer greater than 0 and greater than or equal to the value of watt.server.audit.um.sessionPool.min. The default value is 10.

If you specify an invalid value, Integration Server logs a warning message at start up and then uses the default value at runtime. However, Integration Server does not persist the default value over the invalid value you specified.

Specifies the number of seconds for Integration Server to wait between attempts to re-establish a session on the Universal Messaging server after an audit logger enters queue fail-fast mode. An audit logger enters queue fail-fast mode wdrehen it cannot establish a connection to the Universal Messaging server that contains the audit logging queue. Specify an integer greater than 0 (zero). The default is 30 seconds.

If you specify an invalid value, Integration Server uses the default value at runtime. However, Integration Server does not persist the default value over the invalid value you specified.

Specifies the number of user name and password combinations Integration Server stores in the authentication cache. The default value is 250.

Specifies whether the authentication cache is enabled. When set to true, the authentication cache is enabled. The default value is true.

Specifies the number of milliseconds that each cache entry can remain idle before Integration Server removes it from the authentication cache. The default is 300000 (5 minutes).

When Integration Server receives an HTTP request that includes both an Authorization header and a Cookie header with a session identifier, this parameter specifies whether Integration Server should check that the user identified in the Authorization header is the owner of the session identified in the Cookie header. When set to true (the default), Integration Server confirms that the user of the Authorization header is the owner of the identified in the Cookie header. If the headers do not match, Integration Server returns an HTTP 401 status code with the following message:

The user identified in the request does not own the requested session.

Specifies whether Integration Server performs OAuth authentication when an inbound HTTP/S request includes an access_token in the header fields. Specify true to perform OAuth authentication. Specify false to skip OAuth authentication. The default is true.

Specifies whether Integration Server performs OAuth authentication when an inbound HTTP/S request includes an access_token in the query parameter. Specify true to perform OAuth authentication. Specify false to skip OAuth authentication. The default is true.

Specifies the URL to the SAML artifact resolver endpoint on the My webMethods Server that will be used to validate My webMethods Server users on Integration Server. Along with configuring central user management, the value of this property allows single-sign on for My webMethods Server users. For more information, see Configuring the MWS Single Sign-On Resource Setting.

Specifies whether Integration Server should retain authentication credentials as part of a session. When set to true, Integration Server retains the authentication credentials until the session expires. If set to false (the default), Integration Server deletes the authentication credentials from the session after it handles the initial request from the client.

Specifies whether Integration Server validates requests from Mediator to the native service. When this parameter is set to true, Integration Server skips authentication for Mediator requests. When set to false (the default) Integration Server authenticates all Mediator requests.

Specifies the number of sessions for the default client. The default client is the Broker client that the Integration Server uses to publish documents to the Broker and to retrieve documents delivered to the default client. When you set this parameter to a value greater than 1, the Integration Server creates a new multi-session, shared state Broker client named clientPrefix_DefaultClient_MultiPub, to use for publishing documents to the Broker. Using a publishing client with multiple sessions can lead to increased performance because it allows multiple threads to publish documents concurrently. The default is 1 session.

Specifies the number of reply documents that the Integration Server retrieves from the Broker at one time. Increasing the reply documents the Integration Server retrieves for each call can reduce the number of calls the Integration Server makes to the Broker. The Integration Server maintains all reply documents in memory. You can reduce the amount of memory used for reply documents by decreasing the number of documents the Integration Server retrieves at one time. The default is 5 documents.

Specifies the number of sessions for the request/reply client. The request/reply client is the Broker client that the Integration Server uses to send request documents to the Broker and to retrieve reply documents from the Broker. Increasing the number of sessions for the request/reply client can lead to improved performance because it allows multiple requests and replies to be sent and retrieved concurrently. The default is 1 session.

Specifies how often (in milliseconds) the Integration Server sweeps its internal mailbox to remove expired replies to published requests. The length of the interval should balance the amount of memory consumed by expired replies with retrieving the replies for waiting requests. The Integration Server uses one background thread to age and remove expired replies and uses multiple background threads to retrieve replies for waiting requests. When the sweeper thread removes expired replies, it blocks the threads attempting to retrieve replies. When then sweeper interval is too low, the frequent execution of the sweeper thread can degrade performance because other background threads cannot retrieve replies as often. A sweeper interval that is too high can cause an increase in memory usage because expired replies consume memory for a longer period of time. The default is 30000 milliseconds (30 seconds).

Specifies the number of seconds of idle time that the Broker waits before sending a keep-alive message to Integration Server. If Integration Server does not respond within the amount of time specified by the watt.server.brokerTransport.max property, the Broker sends another keep-alive message to Integration Server. If Integration Server continues to be unresponsive, the Broker continues sending keep-alive messages until it reaches the retry limit specified by the watt.server.brokerTransport.ret property. If the Integration Server still has not responded to the keep-alive message, the Broker explicitly disconnects the Integration Server. The watt.server.brokerTransport.dur value must be an integer greater than or equal to zero but less than 2147483647. The default is 60 seconds.

For more information about using server parameters to configure the keep-alive setting with the Broker, see Setting Server Configuration Parameters for Keep-Alive Mode.

Specifies the number of seconds that the Broker waits for the Integration Server to respond to a keep-alive message. This value must be an integer between 0 and 2147483647. The default is 60 seconds.

For more information about using server parameters to configure the keep-alive setting with the Broker, see Setting Server Configuration Parameters for Keep-Alive Mode.

Specifies the number of times the Broker re-sends keep-alive messages before disconnecting an un-responsive Integration Server. This value must be an integer between 1 and 2147483647. The default is 3 retries.

Specifies the user authorized to prefetch cache service entries. The default is Administrator.

Specifies how often (in minutes) the server sweeps the cache to remove expired cache entries and to prefetch cache service entries. The default is 10 minutes.

Specifies how often (in minutes) the server sweeps the cache to perform garbage collection. The default is 60 minutes.

Specifies the default value for the Maximum Entries in Cache property for a distributed system cache used in an Integration Server cluster. The default is -1 which indicates that Integration Server does not set a default value for the Maximum Entries in Cache property. If you want Integration Server to set a default value for the Maximum Entries in Cache property, you must specify a value greater than 0.

Specifies the number of milliseconds a cache manager will wait while trying to connect to a server specified in the Terracotta Server Array URLs list. The default is 60000 milliseconds (i.e. 60 seconds).

Specifies the location where Ehcache will write log files. The default value of this folder is Integration Server_directory \instances\instance_name\logs\tc-client-logs

Specifies the maximum number of threads that you want Integration Server to use when initializing cache managers at startup.

If the server contains a large number of cache managers, distributed cache managers, or a cache manager with a large number of caches, the registration process at start up could take a long time. To avoid this, you can increase the number of threads used to initialize cache managers by setting the watt.server.cachemanager.parallel.threads property.

If you want Integration Server to initialize cache managers sequentially, set the value to 1. If you want Integration Server to initialize cache managers in parallel, set the value to 2 or higher. Software AG recommends that you do not exceed 10. The default value is 5.

Specifies whether the Central Users component shuts down when it encounters an error. When this property is set to true, the Central User component shuts down when it encounters an error. When the Central Users component shuts down, the Integration Server must be restarted. When this property is set to false, the default, the Central User component does not shut down when it encounters an error.

Specifies whether Integration Server performs ACL checking when a service is directly invoked by a client or trigger and when it is invoked from other services. When set to true, Integration Server always checks the Execute ACL for a service, regardless of the value of the Enforce Execute ACL property for the service. When set to false, the value of the Enforce Execute ACL property determines whether or not Integration Server performs ACL checking when a service executes. The default is false.

Specifies whether the output pipeline should display all the elements in a response when using CGI content handlers to format the responses. When this property is set to false, the output pipeline displays all the elements in the response. When this property is set to true, if the response contains multiple non-string, non-null elements with the same value, the output pipeline will display only the first occurrence of the value. For each of the subsequent occurrences, the output will contain the string, *ObjectRef(className)*. The default is false.

Specifies whether the CGI content handler should use Unicode encoding. When this property is set to false, the CGI content handler will use the encoding specified by the watt.server.netencoding property to encode responses. When this property is set to true, the CGI content handler will use Unicode to encode responses. The default is false.

Specifies the order in which Integration Server scans packages when loading a class file for which no package information is available. When no order is specified, Integration Server attempts to load the class by scanning all packages in the Packages directory, one by one. This could delay class loading. For example, when a trigger contains a reference to a Java class, the trigger does not have any package information. Integration Server scans all the packages for the specific class file in random order. Specifying the packages that Integration Server should scan first may reduce the time needed for class loading.

Use the watt.server.classloader.pkgpriority property to specify a comma delimited list of the packages whose class loader should load first. The syntax for this property is:

For more information about class loading, refer to How the Server Loads Java Classes.

Specifies the amount of time (in minutes) after which an idle user session times out. The default is 10.

Specifies how Integration Server responds when an error at start up prevents Integration Server from joining the cluster. Select one of the following:

The watt.server.cluster.action.errorOnStartup parameter displays the value specified in the Action On Startup Error parameter on the Settings > Clustering and Settings > Clustering >Edit screens of Integration Server Administrator. Software AG recommends that you specify the action to take when Integration Server cannot connect to the cluster on startup using the Action On Startup Error parameter on the Settings > Clustering > Edit screen instead of by changing the value of the watt.server.cluster.action.errorOnStartup parameter.

Specifies a comma-delimited list of aliases for remote Integration Servers in a cluster. The Integration Server uses this list when executing the remote invokes that update the other cluster nodes with trigger management changes. When this property is configured, the Settings > Messaging > webMethods Messaging Trigger Management > Cluster View screen will be visible and the Apply Change Across Cluster check box will be available when performing trigger management tasks.

This parameter is applicable only when you are using webMethods clustering. For more information, see the webMethods Integration Server Clustering Guide.

Specifies whether you want the server to participate in a cluster. A value of true indicates that clustering is enabled for the server. The default is false.

The value of the watt.server.cluster.aware parameter is tied to the value of the Clustering Status field on the Settings > Clustering screen in Integration Server Administrator. Software AG recommends that you use Integration Server Administrator to enable or disable clustering for an Integration Server instead of using the watt.server.cluster.aware property.

This parameter is applicable only when you are using this Integration Server in a cluster.

Specifies the name of the cluster to which Integration Server belongs. If Integration Server does not belong to a cluster, this parameter is empty.

Keep the following in mind when specifying the cluster name:

The watt.server.cluster.name parameter displays the value specified in the Cluster Name parameter on the Settings > Clustering and Settings > Clustering >Edit screens of Integration Server Administrator. Software AG recommends that you specify the cluster name using the Cluster Name parameter on the Settings > Clustering > Edit screen instead of by changing the value of the watt.server.cluster.name parameter.

Specifies number of minutes that the server allows inactive session objects to remain in the cluster store before removing them. The default is 60.

This parameter is applicable only when you are using webMethods Integration Server Clustering. For more information, refer to the webMethods Integration Server Clustering Guide.

A comma-separated list of the Terracotta Server Array URLs that the cluster uses for distributed system caches. This parameter is applicable only when Integration Server belongs to a cluster.

The watt.server.cluster.tsaURLs parameter is tied to Terracotta Server Array URLs parameter on the Settings > Clustering and Settings >Clustering > Edit screen in Integration Server Administrator. Software AG recommends that you specify the Terracotta Server Array URLs using the Terracotta Server Array URLs parameter on the Settings > Clustering > Edit screen instead of by changing the value of the watt.server.cluster.tsaURLs parameter.

Specifies whether Integration Server uses the context loader before using the class loader for the currently executing thread when Integration Server encodes or decodes a pipeline. If a referenced class belongs to a particular package, it may be faster to use the context loader first. The default is false.

Specifies the compiler command that Integration Server uses to compile Java services that are developed using Designer, for example, javac -classpath {0} -d {1} {2}. This compiler command is also used from the jcode utility. If this property is omitted or empty, the server uses the JVM internal Java compile tool to compile Java services.

Specifies whether the jcode utility should stop processing after it fails. If set to true, the jcode utility stops processing at the package on which it fails. If set to false (the default), the jcode utility will continue processing despite the failure.

Specifies from where Integration Server reads compiler errors and warnings. The Software AG webMethods platform includes javac, the Java tool used to compile Java services in Designer and with the jcode utility. The javac compiler returns information about any errors or warnings it encountered during compilation to standard error. If you use the watt.server.compile property to have Integration Server use a different compiler, and that compiler returns errors and warnings to standard out rather than standard error, set watt.server.compile.readFromStdErr to false so that the compiler errors and warnings will be read and displayed to the Java developer. Set watt.server.compile.readFromStdErr to true for Integration Server to read compiler errors and warnings from standard error. The default is true.

Specifies the compiler command that Integration Server uses to compile Java services that are stored in Unicode encoding, for example, javac -encoding Unicode -classpath {0} -d {1} {2}. Note that the setting “javac -encoding Unicode -classpath {0} -d {1} {2}” works with the Oracle JDK compiler. This compiler command is also used from the jcode utility. If this property is omitted or empty, the server uses the JVM internal Java compile tool to compile Java services.

Specifies what content type to use for HTTP requests that do not contain a Content-Type header. The default value is application/octet-stream.

To specify that Integration Server should use a different Content-Type, change the value of watt.server.content.type.default to a different registered content type, such as text/xml or text/html. If you set the value of watt.server.content.type.default to an unregistered content type, Integration Server treats requests with a Content-Type header as if they are text/html.

Changes to this property take effect immediately.

Maps wildcards found in the Accept header field of an HTTP client request to specific content types. The Accept header field specifies which content type or types the client will accept in a response. Integration Server selects an outbound content handler based on the allowed content type. The syntax for this parameter is:

watt.server.content.type.mappings=<wildcard> <content-type>,<wildcard> <content-type>,<wildcard> <content-type> ...

Where:

Use a space to separate the wildcarded content type from the specific content type. Use a comma to separate <wildcard> <content-type> pairs from other pairs. Consider the following examples:

To associate text/* with text/xml, specify:

To associate text/* with text/xml, and multipart/* with multipart/related, specify:

Integration Server parses the Accept header and attempts to select a content type or types as defined in the W3C Hypertext Transfer Protocol specification.

The default setting is text/* text/xml. If this parameter is not specified, and an Accept header field specifies a wildcard, Integration Server selects a content handler based on the major content type specified, as shown below.

The watt.server.http.useAcceptHeader property must be set to true for the watt.server.content.type.mappings parameter to work.

For more information about content handlers, refer to Content Handlers.

Specifies the interval used in conjunction with watt.server.control.controlledDeliverToTrigger.delays to determine the delay that Integration Server applies to services publishing documents locally when the trigger document store reaches 90% of its capacity. The default is 2000.

Specifies a comma-separated list of values specifying the number of milliseconds that Integration Server delays services publishing local documents when the trigger document store is greater than or equal to 90% of its capacity. Integration Server changes the delay based on how long the trigger document store has continuously been at 90% or higher capacity. The default value is 500,2000,3000,3500,4000,4500,5000.

Specifies the trigger queue threshold at which the Integration Server slows down the delivery rate of locally published documents. This threshold is expressed as a percentage of the trigger queue capacity. For example, if you specify 80, the Integration Server decreases the rate at which it delivers locally published documents to a trigger queue when that trigger queue reaches 80% capacity. Integration Server resumes delivering documents at the normal rate when the trigger queue capacity drops below the specified threshold. The default is 90.

Specifies the threshold (as a percentage) at which Integration Server starts to warn of insufficient free memory. When the percentage of available free memory falls below the value of this property, Integration Server generates a warning in the server log. Valid values are 0 to 100. The default is 5.

Specifies the capacity of the outbound document store. Integration Server places published documents in the outbound document store when the configured Broker is unavailable. When the number of documents in the outbound document store equals the capacity, the Integration Server blocks any threads executing services that publish documents. The Integration Server resumes execution of blocked threads after the Broker becomes available. Set this parameter to a whole number greater than 0. The default is 500,000 documents.

Specifies the maximum number of documents that the server can publish on success at one time. For example, suppose that you set the maximum to 100 documents. ServiceA publishes 10 documents on success. ServiceB publishes 90 documents on success. ServiceC publishes 5 documents on success. ServiceA and ServiceB can publish documents concurrently. However, if ServiceC begins to publish documents before ServiceA or ServiceB completes, the Integration Server throws an exception for ServiceC because the documents published by ServiceC exceed the maximum number of documents that can be published on success at one time. If ServiceD publishes 125 documents on success and the maximum is 100, ServiceD will receive an exception every time it executes. The default is 50,000 documents.

The time interval (in milliseconds) at which the Integration Server will check the available free memory. The default is 300000 (5 minutes).

Specifies the threshold at which Integration Server starts to warn of insufficient available threads. When the percentage of available server threads goes below the value of this property, Integration Server generates a journal log message indicating the current available thread percentage and stating "Available Thread Warning Threshold Exceeded." When you receive this message in the journal log, you can adjust the thread usage to make server threads available.

The default is 15%.

Specifies the interval, measured in milliseconds, at which Integration Server will monitor the thread usage. When the percentage of available server threads goes below the threshold value specified in the watt.server.control.serverThreadThreshold property, Integration Server will generate a journal log message to warn of insufficient available threads. The default is 2000 milliseconds.

Specifies the interval used in conjunction with watt.server.control.triggerInputControl.delays to determine the frequency with which Integration Server polls a trigger client queue on the Broker if the queue was empty when it was last polled. The default is 10000.

For more information about controlling the polling frequency for trigger client queues on the Broker, see Delaying Polling Requests for webMethods Messaging Triggers.

Specifies a comma-separated list of values specifying the number of milliseconds that Integration Server delays the polling of a trigger client queue on the Broker. Integration Server changes the delay based on how long the trigger client queues has been empty. The default value is 500,1000,1500,5000.

For more information about controlling the polling frequency for trigger client queues on the Broker, see Delaying Polling Requests for webMethods Messaging Triggers.

Specifies the URIs from which Integration Server is to allow cross-origin requests to access resources.

As recommended by the CORS (Cross-Origin Resource Sharing) standard, Integration Server uses the values of this parameter to validate the request. Integration Server checks the URI specified in the Origin header of the CORS request. If it does not match a URI specified by this parameter, Integration Server refuses the request and returns an HTTP 403 status code with the following message:

If the URI matches a value specified by this parameter, Integration Server sends a response with the CORS Access-Control-Allow-Origin response header back to the requesting user agent.

To define this parameter, enter protocol://hostname or protocol://hostname:portnumber. You can specify the IP address or the name of the machine for hostname. The values are case-sensitive. Use a space or comma delimiter to specify multiple values.

You can use an asterisk (*) to indicate that any URI or origin is allowed.

You can also use regular expressions in the comma-separated list of allowed origin servers which can make the list of origin servers easier to maintain. Integration Server treats any value in the comma-separated list that begins with "r:" as a regular expression. Integration Server treats any value that does not begin with "r:" as a simple string. The server configuration parameter uses the Java regular expression syntax, as documented at https://docs.oracle.com/javase/7/docs/api/java/util/regex/Pattern.html. A regular expression value must match the entire value of the Origin header in the HTTP request for it to be considered a match.

Example:

Integration Server treats the first value, "http://test1.domain.com", as a simple string. If an Origin header contains this value, it will be allowed.

The second value, "r:https?://.*.test2.domain.com:[0-9]+", contains a regular expression. The "r:" is not part of the regular expression. The actual regular expression used to match supplied Origin headers is "https?://.*.test2.domain.com:[0-9]+".

The third value, "r:.+\.[a-zA-Z]*-int.domain.com", contains a regular expression. The "r:" is not part of the regular expression. The actual regular expression used to match supplied Origin headers is ".+\.[a-zA-Z]*-int.domain.com".

"Origin: http://test1.domain.com" will be allowed because it is equal to the first value.

"Origin: http://my.test2.domain.com:8080" will be allowed because it matches the second value.

"Origin: https://my.test2.domain.com:8088" will be allowed because it matches the second value.

"Origin: http://my.test2.domain.com" will not be allowed. If it had a port number, it would match the second value.

"Origin: nbps://example.prod-int.domain.com" will be allowed because it matches the third value.

"Origin: example.qa.staging-int.domain.com" will be allowed because it matches the third value.

"Origin: example.dev1-int.domain.com" will not be allowed. If the second token of the host name did not include any digits, it would have matched the third value.

Regular expressions that match any host name, IP address and port (e.g. "r:.+" and "r:.*") will have the same effect as "*".

Specifies whether Integration Server is to support CORS. If this parameter is set to true, Integration Server allows cross-origin requests. The default value is false.

For more information about using CORS with Integration Server, see Using CORS with Integration Server . For instructions on how to configure Integration Server to allow cross-origin requests, see Configuring Integration Server to Accept CORS Requests.

Specifies the values Integration Server can include with the CORS Access-Control-Expose-Headers header in response to a CORS request. The CORS Access-Control-Expose-Headers header defines the headers that can be exposed to the user agent. Examine your client-side code to determine which response headers, if any, are retrieved by the client and need to be exposed.

The value for this parameter is case-sensitive. Use a space or comma delimiter to specify multiple values. For example:

As determined by the CORS (Cross-Origin Resource Sharing) standard, the following are considered simple response headers and are always exposed: Cache-Control, Content-Language, Content-Type, Expires, Last-Modified, Pragma.

Specifies the host and port on which clients send cross-origin requests to Integration Server. Integration Server uses this value to validate the Host header in the cross-origin request. For improved security, Software AG recommends that you define this parameter if support for CORS is enabled (that is, watt.server.cors.enabled is set to true).

To define this parameter, enter hostname:port or hostname. You can specify the IP address or the name of the machine for hostname. The value for this parameter is case-sensitive. If a value is not provided for this parameter, Integration Server does not validate the Host header in the request. If a value is provided but does not match the Host header in the request, Integration Server returns a 403 response with the message.

Specifies the amount of time in seconds a user agent is allowed to cache the results of a preflight request. Integration Server uses this value in the CORS Access-Control-Max-Age response header.

The default is -1, which indicates the results do not remain on the client. The value must be an integer.

Specifies whether Integration Server is to set the CORS Access-Control-Allow-Credentials header in response to all CORS requests.

When set to true, Integration Server sets the CORS Access-Control-Allow-Credentials header to true in the response. When setting this parameter to true, keep the following points in mind:

When set to false (the default), Integration Server does not set the CORS Access-Control-Allow-Credentials header in the response. When setting this parameter to false, keep the following points in mind:

Specifies the request headers Integration Server will allow in cross-origin requests. Integration Server uses the value to validate the CORS Access-Control-Request-Header request header. If the header is not an exact match of a value specified by watt.server.cors.supportedHeaders, Integration Server refuses the request and returns an HTTP 403 status code with the following message:

If the header matches the value specified by this parameter, Integration Server responds with the CORS header Access-Control-Allow-Headers populated with the value of this parameter.

Examine your server-side code to determine which request headers, if any, are read by your server application and need to be explicitly allowed.

The value for this parameter is case-sensitive. Use a space or comma to separate multiple request headers. For example,

As determined by the CORS (Cross-Origin Resource Sharing) standard, the following are considered simple request headers and are always exposed: Accept, Accept-Language, Content-Type (when the value is application/x-www-form-urlencoded, multiplart/form-data, or text/plain).

Specifies the HTTP methods Integration Server will allow in cross-origin requests. Integration Server uses this value to validate the value of the CORS Access-Control-Request-Method request header. If the header is not an exact match of a value specified by watt.server.cors.supportedMethods, Integration Server refuses the request and returns an HTTP 403 status code with the following message:

If the header matches a value specified by this parameter, Integration Server responds with the CORS header Access-Control-Allow-Headers populated with the value of this parameter.

Use a space or comma to separate multiple HTTP methods. Possible values are OPTIONS, HEAD, GET, POST, PUT, PATCH, and DELETE. Integration Server accepts any of these values by default.

Specifies the file types you do not want Integration Server to include when publishing packages. You can use this parameter to specify the file types to exclude when publishing packages through replication, publishing packages to VCS using the Version Control System Integration feature in Integration Server, and deploying packages. For example, to prevent Integration Server from publishing .svn files, you would specify the parameter as watt.server.createPackage.ignorePattern=.svn.

You can specify several file types using a semi-colon (;) as a delimiter, as follows:

The maximum number of threads maintained for the cronjob-based threadpool, which Integration Server uses for scheduled system tasks. If this maximum number is reached, Integration Server waits until processes complete and return threads to the pool before running more processes. The default is 5.

The minimum number of threads maintained for the cronjob-based threadpool, which Integration Server uses for scheduled system tasks. When Integration Server starts, the thread pool initially contains this minimum number of threads. The default is 2.

Specifies the date format to use in the log files. For the server log, this parameter specifies how the date format is displayed in the server log file as well as in Integration Server Administrator. For all other logs, such as the service, error, session, guaranteed delivery, and security logs, this parameter specifies how the date format is displayed only in Integration Server Administrator.

To specify the date format to use, you can use any format that is supported by the Java class java.text.SimpleDateFormat. For example, to display the date with the format 08-12-02 14:44:33:1235, specify dd-MM-yy HH:mm:ss:SSSS.

Specifies how the server should respond if no input is passed to the pub.date:dateTimeFormat service. When set to true, the server simply returns a null value for the value parameter. The default is for the server to throw an exception.

Specifies the maximum time in milliseconds the server is to block a request when waiting for a connection to a database. (The database must be defined by an alias in the WmDB package.) The default is to wait indefinitely. Specifying -1 also means to wait indefinitely. This property is global to all pools.

Specifies how the server manages connections to a database.

Specifying server tells the server to maintain a pool of connections for each database that is defined to the server through an alias. If a request cannot be satisfied because the pool has reached its maximum number of connections, the server blocks the request and tries again later.

Specifying session tells the server to create a database connection per session. That is, when the server receives a service request that requires a database connection, it will create a new connection if one doesn't already exist for that session; otherwise the server will use the connection that was previously created for that session. If the attempt to create a connection for the session fails, for example because the database has no available slots for connections, the request fails. The default is session.

Although enabling database connection pooling creates a pool for each database defined to your server, you can control the characteristics of each pool individually by using the Edit Alias Information screen of the Integration Server Administrator. See the WmDB User’s Guide for more information about configuring the server to connect to a database.

Specifies how the server handles purging inactive connections that have timed out. With the parameter set to false, the server purges all of these connections. With the parameter set to true, the server purges these connections, but stops when a minimum number of connections in the pool has been reached. You specify the minimum when you define the alias. This property is global to all pools.

Indicates whether the Integration Server ISInternal Functional Alias on the Integration Server Administrator JDBC Pools page refers to the same database that other Integration Servers use, even though the Integration Servers are not clustered. Set this property to true to indicate that the Integration Server shares the same ISInternal database. Setting the property to true is necessary if you want to use guaranteed delivery on multiple Integration Servers that are not clustered but share the ISInternal database. You must set this property to true for all Integration Servers that share the ISInternal database. Set this property to false if the Integration Server does not share the ISInternal database with other Integration Servers. The default is false.

Specifies a SQL statement that can be used to test a database connection in a JDBC connection pool. If the watt.server.db.testSQL parameter specifies a SQL statement, when a caller requests a JDBC connection from a JDBC connection pool, Integration Server executes the specified SQL statement against the database used with the JDBC connection pool. If the SQL statement executes successfully, Integration Server considers the database connection to be valid and returns the connection to the caller. If the SQL statement does not execute successfully, Integration Server considers the database connection to be invalid and removes it from the JDBC connection pool. Integration Server than creates a new JDBC connection, places it in the JDBC connection pool, and returns the new connection to the caller. If no value is specified for watt.server.db.testSQL, Integration Server does not test database connections in the connection pool when a caller requests a JDBC connection. There is no default value for the parameter.

Specifies whether Integration Server checks the FIPS encryption provider every time a user is authenticated. When this parameter is set to true, every time a user is authenticated, Integration Server checks the FIPS encryption provider by using the provider to create a java.security.MessageDigest instance. The provider check writes the name of the provider and the generated MessageDigest to standard error. When set to false, Integration Server does not check the encryption provider every time a user is authenticated. The default is false.

Specifies to which content handlers Integration Server should register the text/html content type. If set to true (the default), then Integration Server registers the text/html content type with the ContentHandler_Default content handler. If set to false, then Integration Server registers the text/html content type with the ContentHandler_CGI content handler.

Specifies the default country, a component of a Java Locale, that Integration Server uses when selecting strings from ResourceBundles to return to a client. Any ISO country code is a valid value. The default value for this property is US. The default locale is en-US.

The default language, a component of a Java Locale, that Integration Server uses when selecting strings from ResourceBundles to return to a client. Any ISO language code is a valid value. The default value for this property is en. The default locale is en-US.

Specifies the name of the default package. If this value is not set, Integration Server uses WmRoot as the default package.

Specifies how the Integration Server logs service exceptions to the Integration Server error log. Set this parameter to true for basic exception logging or false (the default setting) for more detailed exception logging to help pinpoint the source of the exception.

If this parameter is set to true, the cause of the exception becomes more difficult to trace. For this reason, Software AG recommends that you do not set this parameter to true unless you are executing services that catch exceptions and do not rethrow them.

For more information about interpreting the error log and using the log to help debug services, see Debugging Service Exceptions Using the Error Log.

Specifies the maximum number of megabytes of data that Integration Server reads from the file system for an audit log while collecting diagnostic data. This parameter affects the collection of audit log files only. It does not affect audit log data read from the database, nor does it affect other log files such as the server log, stats log or terracotta-client logs. The default is 250 megabytes. You do not need to restart Integration Server for changes to this parameter to take effect.

Specifies how many hours of logs are returned when you run the diagnostic tool. The default is 6. When this property is set to 0, the diagnostic utility does not return any log files. It returns only the configurational and run-time data files.

Specifies the diagnostic port through which you can access Integration Server when it is unresponsive. During installation, Integration Server automatically creates the diagnostic port at 9999. The default is 9999.

If you are running multiple Integration Servers on the same host machine, the diagnostic port on each server must have a unique port number. Set this parameter for each Integration Server instance to use a unique port number. For more information about the diagnostic port and running multiple Integration Server instances, see Adding an HTTP Diagnostic Port.

Specifies whether Integration Server should generate diagnostic files in tabular format. If set to false, Integration Server generates the files in non-tabular format. The default is true.

Specifies how often (in milliseconds) triggers (which are Broker clients) should ping the Broker. When there is a firewall between the Integration Server and the Broker, the firewall closes the connection between a trigger and the Broker when the connection becomes idle. To prevent connections from becoming idle, trigger Broker clients periodically ping the webMethods Broker. The default is 1800000 milliseconds (30 minutes).

Specifies the number of BrokerClient objects that Integration Server can use to communicate with Broker. Integration Server passes this value to set the following Broker API: COM.activesw.api.client.BrokerConnectionDescriptor.setConnectionShareLimit (int value).

For more information, see webMethods Broker Java Client API Reference.

Each Broker connection represents a socket open to the Broker. While decreasing the value of the property can increase throughput, it also increases the number of resources and file descriptors Integration Server uses. Set this parameter to either 0 or a value greater than 1. When set to 0, connection sharing is turned off and each Broker client uses its own Broker connection. The default is 5.

Specifies how often (in milliseconds) that the Integration Server removes state information for completed and expired joins. The default is 1800000 milliseconds (30 minutes).

Specifies whether Integration Server stores and redelivers the original message or a modified message for subsequent trigger service execution when retry failure occurs for a trigger service invoked by webMethods messaging trigger. When set to true, Integration Server stores and redelivers the message originally sent to the webMethods messaging trigger. When set to false, Integration Server stores the message as it is at the point at which retry failure occurs. Integration Server delivers a modified message to the webMethods messaging trigger for subsequent processing. The default is false.

Specifies whether a browser user can view directories that reside on Integration Server without using Integration Server Administrator. When this parameter is set to true (the default), users can view Integration Server directories. When this parameter is set to false, no directories are displayed.

Specifies the default character set used for encoding portions that contain non-ASCII characters in email messages. Email fields that contain non-ASCII characters are subject, MIME headers, body text, and attachments. The pub.client:smtp service uses this property. The default is utf-8. For more information about the pub.client:smtp service, see webMethods Integration Server Built-In Services Reference.

Specifies the email address the server presents as its From address when sending emails about errors. By default, the server uses Integration-Server@localhost for the From Address, where localhost is the name of the host on which the Integration Server is running.

Specifies whether Integration Server should process the reply emails that it receives in its email port if the Subject line of the email contains the prefix "Re:". Set the watt.server.email.processReplyEmails property to true if you want Integration Server to process reply emails that contain the prefix "Re:" along with a valid service name in the Subject line. If the property is set to false, Integration Server does not process the email if the Subject line contains the prefix "Re:". Instead, Integration Server generates a server log message. The default is false.

Specifies whether Integration Server should wait for the email port to complete the processing of a message before returning the thread used to retrieve the message to the thread pool.

When retrieving and processing messages received by an email port, Integration Server uses one thread to retrieve a message and a second thread to execute the service that processes the message. By default, after using a thread to retrieve a message, Integration Server returns it to the server thread pool, making it available to perform other processing.

If the email port receives a large number of messages in a short period of time, the email port might monopolize the server thread pool for retrieving and processing messages. In addition, if the service that processes the messages executes slowly, it is possible that the email port message processing will negatively affect the performance of Integration Server.

To avoid this issue, you can limit the number of threads used to process messages received by an email port by setting the watt.server.email.waitForServiceCompletion property.

When the property is set to true, Integration Server does not return the thread used to retrieve the message to the thread pool until after the service that processes the message executes to completion. As a result, the maximum number of threads used to retrieve and process messages for an email port is equal to 2 or twice the value of the Number of threads if multithreading is turned on field.

When watt.server.email.waitForServiceCompletion is set to false, Integration Server does not wait for the service that processes the message to execute to completion before returning the thread used to retrieve the message to the thread pool.

The default is false.

This is an internal property. Do not modify.

Specifies whether Integration Server assigns a null value to all list data types like Document List, String List, Document Reference List, and Object list during the execution of a flow service without an input value. True indicates that the output of the service assigns a null value for the list data type. False indicates the output of the service would not assign a null value. The default is true.

Specifies the email address to which Integration Server sends messages about critical server log entries. There is no default.

Specifies whether the event handlers for the audit event are invoked asynchronously or synchronously. When this parameter is set to true, Integration Server invokes the event handlers (services) that subscribe to audit events asynchronously. When this parameter is set to false, Integration Server invokes the event handlers that subscribe to audit events synchronously. The default is true.

Specifies whether the event handlers for the exception event, error event, or journal event are invoked asynchronously or synchronously. When this parameter is set to true, Integration Server invokes the event handlers (services) that subscribe to exception events asynchronously. When this parameter is set to false, Integration Server invokes the event handlers that subscribe to exception events synchronously. The default is true.

Specifies whether the event handlers for guaranteed delivery events (gdStart and gdEnd) are invoked asynchronously or synchronously. When this parameter is set to true, Integration Server invokes the event handlers (services) that subscribe to guaranteed delivery events asynchronously. When this parameter is set to false, Integration Server invokes the event handlers that subscribe to guaranteed delivery events synchronously. The default is true.

Specifies whether the event handlers for JMS delivery failure events are invoked asynchronously or synchronously. When this parameter is set to true, Integration Server invokes the event handlers (services) that subscribe to JMS delivery failure events asynchronously. When this parameter is set to false, Integration Server invokes the event handlers that subscribe to JMS delivery failure events synchronously. The default is true.

Specifies whether the event handlers for JMS retrieval failure events are invoked asynchronously or synchronously. When this parameter is set to true, Integration Server invokes the event handlers (services) that subscribe to JMS retrieval failure events asynchronously. When this parameter is set to false, Integration Server invokes the event handlers that subscribe to JMS retrieval failure events synchronously. The default is true.

Specifies whether the event handlers for replication events are invoked asynchronously or synchronously. When this parameter is set to true, Integration Server invokes the event handlers (services) that subscribe to replication events asynchronously. When this parameter is set to false, Integration Server invokes the event handlers that subscribe to the replication events synchronously. The default is true.

Specifies the user who will invoke the service specified in the pub.event.routing:send and pub.event.routing:subscribe built-in services. Integration Server uses the user specified in this parameter only if no user is specified in the runAsUser input parameter of the pub.event.routing:send and pub.event.routing:subscribe services. The default is Administrator.

This user can be defined either internally or in an external directory but must belong to an existing group that has appropriate ACL permissions to invoke the specified service. Integration Server does not validate this user until the service is executed.

The new value of the parameter applies to existing subscriptions as well as new subscriptions created using pub.event.routing:subscribe.

Specifies whether the event handler for security events is invoked asynchronously or synchronously. When this parameter is set to true, Integration Server invokes the event handlers (services) that subscribe to security events asynchronously. When this parameter is set to false, Integration Server invokes the event handlers that subscribe to security events synchronously. The default is true.

Specifies whether the event handlers for session events (sessionStart, sessionEnd, and sessionExpire) are invoked asynchronously or synchronously. When this parameter is set to true, Integration Server invokes the event handlers (services) that subscribe to session events asynchronously. When this parameter is set to false, Integration Server invokes the event handlers that subscribe to session events synchronously. The default is true.

Specifies whether the event handlers for stat (statistics) events are invoked asynchronously or synchronously. When this parameter is set to true, Integration Server invokes the event handlers (services) that subscribe to the statistics events asynchronously. When this parameter is set to false, Integration Server invokes the event handlers that subscribe to the statistics events synchronously. The default is true.

Specifies whether the event handlers for the transaction events (txStart and txEnd) are invoked asynchronously or synchronously. When this parameter is set to true, Integration Server invokes the event handlers (services) that subscribe to transaction events asynchronously. When this parameter is set to false, Integration Server invokes the event handlers that subscribe to transaction events synchronously. The default is true.

Controls whether Integration Server should create a session for the service that is invoked by the Event Manager. When set to true, Integration Server creates a session and associates it with the invoked service. When set to false, Integration Server does not create a session for the service that is invoked by the Event Manager. The default is false.

When watt.server.eventHandlerCreateSession is set to true, watt.server.eventHandlerSessionTimeout specifies the timeout value for sessions created by Integration Server for services that are invoked by the Event Manager. The default value is 60000 milliseconds.

Specifies the maximum number of threads that you want Integration Server to use for the Event Manager thread pool. The default is 5.

Integration Server verifies that this value is greater than watt.server.eventMgr.minThreads. If the value of watt.server.eventMgr.maxThreads is less than the value of watt.server.eventMgr.minThreads, Integration Server sets the value of watt.server.eventMgr.maxThreads to one more than watt.server.eventMgr.minThreads. For example, if watt.server.eventMgr.minThreads is set to 6 and watt.server.eventMgr.maxThreads is set to 5, Integration Server sets the value of watt.server.eventMgr.maxThreads to 7.

Specifies the minimum number of threads that you want Integration Server to use for the Event Manager thread pool. The default is 2.

Integration Server verifies that this value is 1 or greater. If set to a value less than 1, Integration Server resets it to 1.

Specifies the encoding the server is to use when reading and writing text files. This setting has no effect on files stored as Unicode. The default is your JVM's file.encoding property.

Specifies the content of the 220 message that Integration Server returns to an FTP client when the client issues a connect request.

When this parameter is set to true (the default), Integration Server returns the following messages to the FTP client:

When this parameter is set to false, Integration Server returns the following messages to the FTP client:

When this parameter is set to any other value, that value is returned in the 220 message. For example, if you specify Custom FTP connect message, Integration Server will return the following to the FTP client:

Specifies the number of seconds that must elapse before a file that has been updated or created on an Integration Server functioning as an FTP server can be accessed. Files created or updated within the time specified by this parameter will not be part of the results of the FTP LIST command. The default value is 60 seconds.

Specifies the content of the 230 message that Integration Server returns to an FTP client when the client issues a login request.

When this parameter is set to true (the default), Integration Server returns the following message to the FTP client: 230 User userid logged in.

When this parameter is set to false, Integration Server returns the following message to the FTP client: 230

When this parameter is set to any other value, that value is returned in the 230 message. For example, if you specify Custom FTP login message, Integration Server will return the following to the FTP client:

Specifies the content of message 215 that Integration Server returns to an FTP client when the client issues a system request. When this parameter is set to true (the default), Integration Server returns the following message to the FTP client:

When this parameter is set to false, Integration Server returns the following message to the FTP client:

When this parameter is set to any other value, that value is returned in the 215 message. For example, if you specify Custom FTP system message, Integration Server returns the following to the FTP client:

Controls whether the pub.client:ftp service uses connection information from a NAT server when connecting to an FTP server.

When the pub.client:ftp service tries to transfer data to or from an FTP server, Integration Server first connects to the FTP server at the IP address specified by the pub.client:ftp service. In response, the FTP server sends back the IP address on the FTP server to which Integration Server should connect to perform the transfer. If the FTP server sits behind a NAT server, the NAT server intercepts this address, translates it, then sends it on to Integration Server.

This property controls whether Integration Server uses the address provided by the NAT server or the address already specified by the pub.client:ftp service.

When this parameter is set to true, Integration Server bypasses the translated address and tries the address specified by the service. If this attempt fails, Integration Server throws an exception.

When this parameter is set to false, the default, Integration Server tries the address provided by the NAT server. If that attempt fails, Integration Server tries the IP address specified on the pub.client:ftp service. If both attempts fail, Integration Server throws an exception.

Specifies IP access for ports that do not have a custom IP access setting. When this parameter is set to include, the server accepts requests from all IP addresses, except those specifically denied on the Integration Server Administrator interface. When this parameter is set to exclude, the server denies requests from all IP addresses except those specifically allowed on the Integration Server Administrator interface. The default is include.

Specifies the name of the host that is allowed service. There is no default.

This is an internal property. Do not modify.

This is an internal property. Do not modify.

Indicates whether Integration Server allows a client to use the HTTP OPTIONS method to determine the HTTP methods supported by Integration Server. When this parameter is set to true, Integration Server allows the OPTIONS method. When this parameter is set to false (or any other value), OPTIONS requests from clients receive a ”405 Method Not Allowed” response.

The default is true.

Specifies the encoding that the HTTP client (such as a browser) uses when encoding the user name and password for Integration Server. The HTTP client sends the user name and password to Integration Server in the Authorization attribute in the header of the HTTP request. Set the watt.server.http.authorizationEncoding property to the encoding that your browser uses for the Authorization attribute. Consult the browser documentation, or contact the browser manufacturer, to find what encoding is used in your environment. The default is UTF-8.

Specifies whether Integration Server includes the HttpOnly attribute in the Set-Cookie header in the response to an HTTP client. When this property is set to true (the default), Integration Server includes the HttpOnly attribute in the Set-Cookie header of the HTTP response to an HTTP client. Software AG recommends setting this property to true because it prevents a client side script from accessing a protected cookie. If you are working with an HTTP client that does not support the HttpOnly attribute, set this property to false.

Specifies whether Integration Server includes the secure attribute in the Set-Cookie header in the response to an HTTP/S client. When the watt.server.http.header.useSecure property is set to true (the default), Integration Server includes the secure attribute in the Set-Cookie header of the HTTPS response to an HTTP/S client. Software AG recommends setting this property to true because it ensures that the cookie is always encrypted while being transmitted from client to server.

Specifies whether an HTTP interceptor is enabled for Integration Server When set to true, Integration Server uses the HTTP interceptor implementation identified in watt.server.http.interceptor.impl to intercept all HTTP requests and HTTP responses. When set to false, Integration Serverdoes not use an HTTP interceptor. The default is false.

Specifies the fully qualified name of the java class for the HTTP interceptor implementation. The provided class must implement the com.softwareag.is.interceptor.HttpInterceptorIFC interface and provide implementations of both methods in the class (preprocess and postProcess). The file for the HTTP interceptor implementation must be available on the server classpath.

Specifies the maximum number of bytes that an HTTP interceptor reads during preprocessing. If the HTTPRequest's input exceeds this value, the HTTP interceptor reads up to this limit and then ignores the rest of the input stream. The default is -1, which indicates that there is no limit to the number of bytes that the HTTP interceptor reads during preprocessing. The HTTP interceptor will read the entire input stream.

Specifies how Integration Server handles JSON content in HTTP client requests. When this property is set to parsed (the default), Integration Server parses JSON content into pipeline variables automatically. Clients can then use JSON to compose pipelines and execute existing services without having to call pub.json:jsonStreamToDocument.

If watt.server.http.jsonFormat is set to stream, Integration Server places a jsonStream variable containing the JSON content in the pipeline as an InputStream. You can then use pub.json:jsonStreamToDocument to parse jsonStream into pipeline variables.

If watt.server.http.jsonFormat is set to bytes, Integration Server places the incoming stream of JSON into a byte array.

You can override the behavior specified by watt.server.http.jsonFormat in individual requests by adding the jsonFormat query parameter to the request URI. For example, if watt.server.http.jsonFormat is set to parsed, a client can override this setting and instead specify a value of stream for the request by entering a URI as follows:

This will result in the request being placed in a jsonStream variable in the pipeline as an InputStream containing the JSON content.

Specifies how Integration Server handles duplicate query tokens in an HTTP request.

Specifies whether Integration Server should decode percent-encoded URI paths in requests before evaluating URI paths. When this property is set to true (the default), Integration Server defers decoding percent-encoded reserved characters until after evaluating URI paths. When set to false, Integration Server decodes percent-encoded reserved characters prior to evaluating the URI paths.

Specifies a semicolon-delimited list of HTTP clients from which you want Integration Server to request re-authentication after an HTTP session expires. By default, this parameter is set to Firefox;MSIE so that requests from the Mozilla Firefox and Microsoft Internet Explorer browsers will be asked to re-authenticate if the associated HTTP session has expired. For user agents not specified on this list, Integration Server sends a new session cookie when the session expires.

If you remove this property and restart Integration Server, the value of this property resets to Firefox;MSIE.

Specifies whether Integration Server should return a stack trace in the HTTP/SOAP response it sends to the invoking client when an invoked service ends in error. You can specify one of the following:

Specifies the name of the Integration Server security realm. This value is included in the headers of HTTP responses that Integration Server sends to clients that request authentication. The default value is Integration Server.

Specifies whether or not the '+' character is interpreted as a ' ' when it appears in the path component of the request URI using the new configuration property. When set to true, the default, Integration Server converts '+' to ' ' when processing the request URI. When set to false,Integration Server does not convert '+' to ' ' when processing the request URI. This setting affects only the handling of '+' characters in the request URI's path component. Any '+' characters that appear in the request URI's query will be converted to ' ' characters regardless of the value of watt.server.http.uriPath.decodePlus.

Specifies whether Integration Server supports the Accept header field in an HTTP request. The Accept header field specifies a content type or types the HTTP client will accept in the HTTP response. The default setting is true. This parameter must be set to true if you want to use the watt.server.content.type.mappings parameter to map wildcard content types in the Accept header field to specific content types.

Controls how Integration Server is to handle the X-Frame-Options attribute in response headers.

Set this parameter to one of the following values:

If you do not want Integration Server to include the X-Frame-Options attribute in response headers, remove the value from the watt.server.http.x-frame-options property. For example: watt.server.http.x-frame-options= The property can be set on the Settings > Extended page of Integration Server Administrator. Changes to this property take effect immediately; the server does not need to be restarted.

Specifies whether Integration Server parses incoming XML documents automatically or passes them directly to the service. Use this property to set the default behavior for how Integration Server should pass XML documents via HTTP. Specify one of the following values:

If a value for watt.server.http.xmlFormat is not specified or is invalid, the default XML parsing behavior is "node".

This feature can be used when submitting and receiving XML via HTTP of HTTPS only.

Specifies whether Integration Server should log outbound HTTP/HTTPS requests to a separate log file. If set to true, Integration Server creates the Integration Server_directory \instances\instance_name\logs\http.log file, which logs data for HTTP/HTTPS requests. The http.log file is created separately from the data captured in the server log. The default is false.

Integration Server logs the following in http.log:

Specifies the name of the host that is denied service. There is no default.

Specifies the interval, measured in minutes, at which the scheduled system service Message History Sweeper executes and removes expired document history entries. The default is 10 minutes.

Specifies the characters that you cannot use when naming a package, folder or service. The default is ?`-#&@^!%*:$.\ /';,~+=)(|}{][><.

Specifies characters that you cannot use in user names and passwords. The default is "\<&.

Specifies the IP address on which the server is to listen for incoming requests. By default, Integration Server listens on all available IP addresses. To limit the server to listening on a single IP address, specify the IP address as the value of this property.

Specifies an alternative word to use for the invoke directive in URLs that invoke services on Integration Server. By default, this parameter is set as watt.server.invokeDirective=invoke, which means users must specify the invoke directive as invoke (http://host:port/invoke/folder/service_name). To allow users to specify the invoke directive as either invoke or an alternative word, set this parameter to the alternative word. For example, to allow users to specify the invoke directive as either invoke or submit, (http://host:port/invoke/folder/service_name or http://host:port/submit/folder/service_name ), set this parameter as watt.server.invokeDirective=submit.

Specifies the total amount of waiting time (in milliseconds) that can elapse if the Integration Server makes the maximum attempts to retry a service. The default is 15,000 milliseconds (15 seconds). When configuring retries for an individual service, the value calculated by multiplying Max attempts value by the Retry interval cannot exceed the value set by this server parameter. For more information about configuring service retry, see webMethods Service Development Help.

Specifies whether the source code for Java services is stored in Unicode encoding. The default is false. Set this value to true if the source code contains characters that cannot be rendered in the server's native encoding.

Specifies the wait time, measured in milliseconds, that elapses before Integration Server interrupts a connection creation thread that is in a wait state. There is no default value.

Specifies the maximum number of milliseconds that a thread can take while creating or closing a connection before the pool interrupter thread interrupts the thread. After the specified time elapses, the pool interrupter thread considers the thread to be blocked and interrupts it. There is no default value. The pool interrupter thread, which is a monitoring thread for the connection pool, only executes if this server configuration property has a value that is greater than zero.

Specifies the number of milliseconds the pool interrupter thread sleeps between sweeps for server threads that became blocked while creating or closing a connection. When the sleep time elapses, the pool interrupter thread, which is a monitor thread for the connection pool, checks for server threads that became blocked while attempting to create or close a connection from the connection pool. The default is 2000 milliseconds.

When enabled, this property represents the percentage value that is used in addition to the configured maximum number of connections (set by the Maximum Pool Size parameter on the Connections page) for the connection pool. For example, setting the property as watt.server.jca.connectionPool.thresholdWaitingRequest=20 sets the threshold to 120% of configured maximum number of connections.

If the property is not defined or if the value is less than or equal to zero, the feature remains disabled.

When this property is enabled, the connection pool ensures that the waiting connection requests plus the busy connections in the connection pool do not exceed the threshold limit.

If Integration Server cannot store the status of a transaction and its participating resources in the XA recovery store (for example, because the store is corrupted), specifies whether Integration Server should try to continue with the transaction anyway (false) or try to roll it back (true). Setting the parameter to false involves some risk; if Integration Server ends abnormally, no statuses will have been saved to the XA recovery store, and Integration Server will not be able to resolve the uncompleted transaction or give you the chance to resolve it manually.

Specifies whether Integration Server maintains XA transaction information for use with XA transaction recovery. If Integration Server does not save XA transaction information, uncompleted XA transactions cannot be recovered using Integration Server. That is, Integration Server does not attempt to recover incomplete XA transactions automatically and you cannot use Integration Server Administrator to manually recover or resolve an incomplete transaction. Specify true to enable XA transaction recovery. Specify false to disable XA transaction recovery. The default is true.

Specifies the default settings for the DataDirect Snoop tool for DataDirect Connect JDBC drivers. The DataDirect Snoop tool logs network packets between Integration Server and an external RDBMS. The resulting log file can be used for tracing and diagnostic purposes.

Set this parameter on each DataDirect Connect JDBC driver for which you want to log data.

The default value for this parameter is:

Where <alias_name> is the name of the JDBC connection pool alias.

The default value defines the name and location of the log file and DataDirect Snoop tool attributes. Typically, you do not need to change the default value. However, you can modify the value if the attributes do not meet the needs of your system. If you change the log file location, be aware that the diagnostic tool collects data from the Integration Server_directory /instances/instance_name/logs/snoop directory. If you change the log file location, the diagnostic utility might not import the data logged by the DataDirect Snoop tool. For more information about using the diagnostic utility, see Using the Diagnostic Utility. For more information about setting the DataDirect Snoop tool attributes, consult the documentation on the DataDirect website.

Specifies the default settings for the DataDirect Spy diagnostic feature for DataDirect Connect JDBC drivers. DataDirect Spy logs JDBC calls and SQL statement interactions between Integration Server and an external RDBMS. The resulting log file can be used for tracing and diagnostic purposes.

Set this parameter for each DataDirect Connect JDBC driver for which you want to log data.

The default value for this parameter is:

Where <alias_name> is the name of the JDBC connection pool alias.

The default value defines the name and location of the log file and DataDirect Spy attributes. Typically, you do not need to change the default value. However, you can modify the value if the attributes do not meet the needs of your system. If you change the log file location, be aware that the diagnostic tool collects data from the Integration Server_directory /instances/instance_name/logs/spy directory. If you change the log file location, the diagnostic utility might not import the data logged by DataDirect Spy. For more information about the diagnostic utility, see Using the Diagnostic Utility. For more information about setting DataDirect Spy attributes, consult the documentation on the DataDirect website.

For use with WmDB. Specifies the name of the Java class for the driver you want to use to connect to databases when no driver name is supplied for a database alias.

Specifies the length of time, in milliseconds, that Integration Server waits for a commit to the embedded database to complete before removing the associated connection from the connection pool. Integration Server uses this property when it is configured to use the embedded database for any of the ISInternal, DocumentHistory, and Xref functions. If the commit process takes longer than the value defined by this property, Integration Server removes the associated connection from the connection pool so that a new connection can be initiated for future requests. The default value for this property is 150 milliseconds.

Specifies a comma-delimited list of JDBC drivers you want the server to load when it initializes. There is no default.

Specifies the name of the log file that contains JDBC log activity. When the watt.server.jdbcLogging property is enabled (set to on), the server logs activity to this file. The default value is jdbc.log. It is located in the Integration Server_directory \instances\instance_name\logs folder. Note that the log file is generated after WmDB makes a connection to the database.

Sets the maximum time, in seconds, that the JDBC driver on Integration Server is to wait for a response while attempting to connect to a database. If Integration Server does not receive a response in the allotted time, it terminates the request, logs the error and moves on. The default value is 60 seconds.

If Integration Server is unable to connect to the audit logging database within the number of seconds specified by watt.server.jdbc.loginTimeout, Integration Server removes all connections from the ISCoreAudit JDBC connection pool and recreates them. If the connection problem is resolved quickly (such as a momentary network interruption), Integration Server reconnects to the audit logging database. If Integration Server is unable to connect to the audit logging database, such as when the database is offline, Integration Server writes an exception to the server log.

Specifies whether Integration Server is to enable logging on java.sql.DriverManager in order to log JDBC activity. When set to on, the server writes the log file data to the file specified by watt.server.jdbcLogFile. The default is off.

Specifies if the Integration Server is to process the stored procedure results from a single result set or multiple result sets. When set to true, Integration Server processes and returns information produced by multiple result sets. When set to false, Integration Server processes information produced from a single result set. The default is false.

Specifies whether the $data input parameter of the pub.db:call service expects values to invoke a stored procedure through the pub.db:call service. Set this property to false if you do not want to specify values for the $data input parameter. Set this property to true if you want the pub.db:call service to expect values for the $data input parameter. The default is true.

Specifies whether Integration Server is to cache prepared statements for later use. When set to true, the server saves prepared statements in a local cache. When the server receives subsequent requests to a database, it can reuse the prepared statements in the cache instead of recreating them each time a request is made. To use Java heap space efficiently, the server removes cached statements automatically if it is not reused within 30 seconds. The default is false.

Specifies the number of attempts to redeliver a document from the client side queue. Specify a positive integer value. The default is 5. If Integration Server is unable to deliver the document in the configured number of attempts, the document is dropped from the client side queue and not delivered. In this situation, Integration Server raises a JMSDeliveryFailureEvent.

Specifies the frequency (measured in seconds) with which Integration Server checks the state of a connection to the JMS provider. The minimum is 1 second. If this parameter is set to less than 1, Integration Server uses the default value instead. The default is 45 seconds.

Configures Integration Server to send a keep-alive message to a destination on the JMS provider, thereby preventing the firewall from terminating the connection between Integration Server and a third-party JMS provider. A keep-alive message is a blank, non-persistent JMS message with an immediate time out.

Set this parameter to one of the following values:

Specifies how often, measured in seconds, Integration Server should ping the JMS provider. The ping serves as a keep alive request sent to the JMS provider. The default is 300 seconds (5 minutes).

Specifies the length of time, in seconds, that Integration Server waits between connection attempts when a connection to the JMS provider or JNDI provider fails. The default is 20 seconds.

Specifies the maximum amount of time, measured in milliseconds, that a pub.jms* service will wait for a connection while the connection used by the service is being updated. If Integration Server does not restart the connection before the blocking time elapses, Integration Server throws an ISRuntimeException and the sending service fails. A value of 0 (zero) indicates that Integration Server does not block the pub.jms* services while the JMS connection alias updates; Integration Server throws an ISRuntimeException immediately. The maximum value is 10,000 milliseconds (10 seconds). The default is 1000 milliseconds.

Integration Server resets the watt.server.jms.connection.update.blockingTime parameter to the default value if an invalid value is entered.

Specifies the length of time, measured in milliseconds, Integration Server waits for services sending JMS messages to execute to completion when the connection used by the services needs to be updated. After the restart delay elapses, Integration Server refreshes the connection using the updated connection factory object and then restarts the connection. If the restart delay elapses before the pub.jms*services execute to completion, Integration Server throws an ISRuntimeException and the sending service fails. The maximum value is 10,000 milliseconds (10 seconds). The default is 500 milliseconds.

Integration Server resets the watt.server.jms.connection.update.restartDelay parameter to the default value if an invalid value is entered.

Specifies the maximum number of messages Integration Server retrieves from the client side queue and then sends to the JMS provider. Integration Server places sent messages in the client side queue when the connection to the JMS provider fails. Integration Server begins to drain the client side queue after the connection to the JMS provider becomes available. The default is 25.

Enables an extra level of verbose logging for JMS triggers that can be controlled globally or at the individual JMS trigger level.

Specifies whether or not Integration Server always uses XA transaction logging when sending a JMS message in accordance with a multisend guaranteed policy. In XA transaction logging, Integration Server logs the state of each transaction. The XA transaction logging allows Integration Server to recover any transactions that did not complete due to Integration Server failure. While this is the most reliable way to ensure the integrity of a transaction, it may be expensive in terms of performance and may not always be necessary. When this property is set to true, Integration Server always uses XA transaction logging and can perform XA transaction recovery for a multisend guaranteed policy regardless of the connection transaction type When set to false, Integration Server uses XA transaction logging only if the connection transaction type is XA_TRANSACTION. The default is false.

Specifies whether the client ID of the JMS connection alias will be used as the prefix in the names of durable subscribers created using Designer. Set to true to use the value of the Client ID property in the JMS connection alias as a prefix in the durable subscriber name. Even if the watt.server.jms.nirvana.durableSubscriber.includeClientId is set to true, if the Client ID property is empty the durable subscriber name will not have a client ID prefix. Set to false to omit the use of the client ID as a prefix. The default is true.

Specifies the number of milliseconds for which an inactive entry remains in the default session pool or a destination-specific pool before Integration Server removes the entry. Integration Server uses this value when -1 is specified for the Idle Timeout field for a JMS connection alias. The default is 60000.

Specifies the consecutive number of successful requests for more messages that a concurrent JMS trigger must make before the trigger becomes multithreaded. For example, when this property is set to 1000, Integration Serverbegins using multiple threads for a concurrent JMS trigger when the JMS trigger retrieves messages fro the JMS provider in 1000 consecutive requests. The default for this property is 0, which indicates that Integration Server does not use a threshold to determine when JMS trigger become multithreaded. When threshold is not used, the concurrent JMS trigger will always be multithreaded when more than one message is available for processing. For more information about using a threshold for thread usage for a concurrent JMS trigger, see Establishing a Threshold for Using Multiple Threads with a Concurrent JMS Trigger.

Specifies the lengthy of time (in milliseconds) for which the primary server thread for a concurrent JMS trigger polls the JMS provider for more messages. Each concurrent JMS trigger has a server thread that retrieves messages from the JMS provider. This thread is considered to be the primary thread for the concurrent JMS trigger. A short polling interval increases the amount of CPU used by Integration Server and increases the load on the JMS provider. However, a short polling interval can improve performance under heavy load and in request-reply scenarios. The default is 500 milliseconds.

If a value of 0 is specified, Integration Server uses the javax.jms.MessageConsumer.receiveNoWait() API to retrieve messages from the JMS provider. The javax.jms.MessageConsumer.receiveNoWait() API may or may not be supported by all JMS providers. If the JMS provider from which a JMS trigger receives messages does not support this API then the JMS trigger will be disabled. If this happens, modify the value of watt.server.jms.trigger.concurrent.primaryThread.pollingInterval to be a positive integer. and enable the JMS trigger.

Specifies the lengthy of time (in milliseconds) with which the secondary server threads for a concurrent JMS trigger poll the JMS provider for more messages. The secondary server threads are the additional threads that can be used to retrieve messages for a concurrent JMS trigger. The number of secondary server threads for a concurrent JMS trigger corresponds to the value Max execution threads property value minus 1. A short polling interval increases the amount of CPU used by Integration Server and increases the load on the JMS provider. A long polling interval can impact the time required for Integration Server to shut down as Integration Server must wait for the polling interval to elapse for each secondary thread used by concurrent JMS triggers. The default value is 1 millisecond.

The value of watt.server.jms.trigger.concurrent.secondaryThread.pollingInterval must be less than or equal to the value of watt.server.jms.trigger.concurrent.primaryThread.pollingInterval.

If a value of 0 is specified, Integration Server uses the javax.jms.MessageConsumer.receiveNoWait() API to retrieve messages from the JMS provider. The javax.jms.MessageConsumer.receiveNoWait() API may or may not be supported by all JMS providers. If the JMS provider from which a JMS trigger receives messages does not support this API then you may see unexpected behavior. If this happens, modify the value of watt.server.jms.trigger.concurrent.secondaryThread.pollingInterval to be a positive integer.

Specifies the time interval, measured in milliseconds, at which Integration Server introduces the polling delay for an inactive concurrent JMS trigger. If the JMS trigger remains inactive, the same time interval determines when Integration Server increases the extended delay. The default value is 0 which indicates that Integration Server does not use an extended polling delay for inactive concurrent JMS triggers. For more information about delaying polling requests, see Delaying Polling Requests for Concurrent JMS Triggers.

Specifies the length of the delay that an inactive concurrent JMS trigger waits before polling the JMS provider for more messages. To increase the delay while the JMS trigger remains inactive, specify a comma-separated list of increasing integers. The watt.server.jms.trigger.extendedDelay.delays parameter is measured in milliseconds and has a default value of: 0, 1000, 2000, 3000.

For more information about delaying polling requests, see Delaying Polling Requests for Concurrent JMS Triggers.

Specifies the group tag used in the names of JMS triggers that belong to a trigger group. Integration Server treats JMS triggers with the specified group tag in the name as members of a trigger group. All triggers in a trigger group use the following format for the name: folder.subfolder:originalJmsTriggerName_groupTag_Id

The default is WMTG. If you set the parameter to null(blank), Integration Server does not use trigger groups and the methods in the com.wm.app.b2b.server.jms.consumer.JMSTriggerGroupFacade class cannot be used to create triggers.

Specifies the maximum number of times the JMS provider can deliver a message to Integration Server. The default is 100.

Specifies the maximum number of messages that the webMethods Broker API for JMS will retrieve and cache per request for a JMS trigger. Using pre-fetch cache can speed up the retrieval of messages from the webMethods Broker. Because messages will be placed in Integration Server memory, you may want to decrease this setting if you have JMS triggers receiving very large messages. Otherwise, memory issues can occur. This property only applies to JMS triggers receiving messages from the webMethods Broker. The default is 10 messages.

Integration Server checks this value when a JMS trigger starts. To apply a new value to all JMS triggers, use Integration Server Administrator to disable and then enable JMS triggers. For information about using Integration Server Administrator to disable and enable an individual trigger, see Managing JMS Triggers.

This property only takes effect when the trigger's prefetch property is set to -1.

When working in a cluster of Integration Servers, the behavior controlled by this property might appear at first to be misleading. For example, suppose that you have a cluster of two Integration Servers. Each Integration Server contains the same JMS trigger. Twenty messages are sent to a destination from which JMS trigger receives messages. It might be expected the JMS trigger on Integration Server 1 will receive the first message, the JMS trigger on Integration Server 1 will receive the second message, and so forth. However, what may happen is that the JMS trigger on Integration Server 1 will receive the first 10 messages and the JMS trigger on Integration Server 2 will receive the second 10 messages.

Specifies the interval, measured in seconds, at which Integration Server executes resource monitoring services for JMS triggers. A resource monitoring service is a service that you create to check the availability of resources used by a JMS trigger service. After Integration Server suspends a JMS trigger because all retry attempts have failed, it schedules a system task to execute the resource monitoring service assigned to the JMS trigger. The default is 60 seconds. Changes to this property take effect the next time Integration Server schedules a system task to execute a resource monitoring service for a JMS trigger.

For more information about building resource monitoring services for JMS triggers, see Using webMethods Integration Server to Build a Client for JMS.

Specifies the frequency (measured in minutes) with which Integration Server refreshes an inactive connection for a JMS trigger. A JMS trigger session is considered to be inactive when the JMS trigger does not use the session to retrieve messages. The default is 30 minutes.

Specifies the length of time, in milliseconds, that an inactive pooled consumer remains in the consumer pool before it is removed. Integration Server uses a pool of consumers to retrieve and process messages for concurrent JMS triggers. When the timeout value elapses, Integration Server deletes the inactive pooled consumer. For the Integration Server to retrieve more messages for the concurrent JMS trigger, Integration Server must create a new consumer, which entails creating a javax.jms.MessageConsumer and javax.jms.Session. For some JMS providers, this can be an expensive operation. Setting a high value for watt.server.jms.trigger.pooledConsumer.timeout server property results in the JMS session and messageConsumer remaining open for a long period of time. If the load on Integration Server is high, a long timeout value reduces the frequency with which the pooled consumers must be created. However, when the timeout value is high and the load on Integration Server is low there may be unused pooled consumers.There is no default timeout value.

Indicates whether Integration Server generates a JMS retrieval failure event when a JMS trigger experiences a fatal exception, such as a non-transient error or a message that cannot be reprocessed, during message processing. Specify true if you want Integration Server to generate a JMS retrieval failure event. The default is true.

Indicates that Integration Server generates a JMS retrieval failure event when a JMS trigger experiences a retry failure. A retry failure can occur when the JMS provider has reached the max delivery count for a message or when an ISRuntimeException is thrown and the JMS trigger is not configured to recover the message (for example, if retry failure handling for a non-transacted JMS trigger is set to "Throw exception" instead of "Suspend and Retry Later".) When set to true, Integration Server generates a JMS retrieval failure event for a JMS trigger when retry failure occurs. The default is true.

Determines whether or not Integration Server attempts to re-enable JMS triggers automatically when an error unrelated to the connection to the JMS provider causes the JMS trigger to be disabled. Set watt.server.jms.trigger.retryOnConsumerError to true to instruct Integration Server to re-enable JMS triggers automatically. Set the property to false to instruct Integration Server to leave JMS triggers disabled when the message consumer encounters an unexpected error unrelated to the connection to the JMS provider. The default is true.

Specifies whether or not sessions can be reused across multiple transactions for a transacted JMS trigger. When set to true, a transacted JMS trigger will reuse the same JMS session for receiving messages from the JMS provider. When set to false, Integration Server creates and closes a session for each message a transacted JMS trigger receives and processes. The default value is true.

Some JMS providers might not support the use of a single session across multiple transactions. When working with these JMS providers, set watt.server.jms.trigger.reuseJmsTxSession to false.

Indicates whether instances of a JMS trigger use the same session on Integration Server. When this property is set to true, the JMS trigger uses a shared session. Each of the trigger services executed by the JMS trigger will use the same session ID. When this property is set to false, Integration Server uses a new session for each instance of a JMS trigger. Reusing sessions for a JMS trigger might improve performance. However, this property does not work with all adapters. If you are working with an adapter, such as the SAP adapter, that requires the session ID to be unique, set this property to false. The default is false.

Specifies the length of time (in milliseconds) for which the server thread for a serial JMS trigger polls the JMS provider for messages. A short polling interval increases the amount of CPU used by Integration Server and increases the load on the JMS provider. However, shorter polling intervals can improve performance under heavy load and in request-reply scenarios. The default is 500 milliseconds.

If a value of 0 is specified, Integration Server uses the javax.jms.MessageConsumer.receiveNoWait() API to retrieve messages from the JMS provider. The javax.jms.MessageConsumer.receiveNoWait() API may or may not be supported by all JMS providers. If the JMS provider from which a JMS trigger receives messages does not support this API then the JMS trigger will be disabled. If this happens, modify the value of watt.server.jms.trigger.serial.primaryThread.pollingInterval to be a positive integer and then enable the JMS trigger.

Determines the maximum number of retry attempts that Integration Server makes to start a JMS trigger after the trigger fails to start. After the initial trigger startup failure, Integration Server waits an interval of 1000 milliseconds and then retries starting the trigger. If startup of the trigger fails, Integration Server waits 1000 milliseconds and then makes another attempt to start the trigger. Integration Servercontinues in this way until the JMS trigger starts successfully, the JMS connection alias stops running, or the JMS trigger becomes disabled. When starting the trigger fails after Integration Server makes the maximum number of retry attempts, Integration Server can take no further action to start the trigger. Integration Server logs an exception which will be visible in the JMS Trigger Management page of Integration Server Administrator. The JMS trigger remains inactive until the problem is resolved and the trigger is manually restarted (i.e. enabled).

The watt.server.jms.trigger.startupFailure.retryCount parameter must be set to an integer greater than or equal to 0. When the parameter is set to 0, the default, Integration Server does not make any retry attempts. Excessive retry attempts may cause the JMS connection alias startup time to be delayed.

Specifies the maximum amount of time, measured in seconds that Integration Server waits after a JMS trigger is disabled before forcing the JMS trigger to stop processing messages. The minimum value is 0. The default is 3 seconds.

You can disable a JMS trigger by invoking the pub.trigger:disableJMSTrigger service or by using or via the Settings > Messaging > JMS Trigger Management screens in Integration Server Administrator. For information about disabling JMS triggers, see About JMS Trigger Status and State.

When you save a JMS trigger in Designer, Integration Server stops and then restarts the trigger. In this situation, Integration Server waits 3 seconds before forcing the JMS trigger to stop processing messages. This value cannot be configured.

Indicates that Integration Server attempts to receive messages from durable subscribers in a load-balanced fashion. When set to true, Integration Server does the following:

This property only applies when the JMS trigger uses a JMS connection alias that connects to the webMethods Broker using the native webMethods API.

The default is true.

Specifies the amount of time (measured in milliseconds) that Integration Server waits for the next portion of an input stream before throwing WmReadTimeoutException. The read timeout only applies after Integration Server retrieves the initial piece of the input stream. The default is 30000 milliseconds.

Specifies the maximum number of records that Integration Server displays when searching for users or groups in the LDAP or central directory and no search criteria are specified. The default is 0. When set to 0, Integration Server displays all available records.

The JSON standard requires that field names be enclosed in double quotes. However, when parsing legacy JavaScript as JSON text it may be helpful to allow unquoted field names as JavaScript does not require field names to be enclosed in double quotes. If this parameter is set to true, the pub.json:jsonStringToDocument and pub.json:jsonStreamToDocument services allow unquoted field names in any supplied JSON text. If this parameter is set to false, the services throw a ServiceException when encountering unquoted field names. The default is false.

The watt.server.json.allowUnquotedFieldNames parameter also affects the process of creating document types from a JSON text. If watt.server.json.allowUnquotedFieldNames is set to true and a JSON text with unquoted fields is used as the source for a document type, the resulting document type contains fields that correspond to the unquoted fields as well as the quoted fields. When watt.server.json.allowUnquotedFieldNames is set to false and a JSON text with unquoted fields is used as the source for a document type, Designer throws an exception and does not create the document type.

Converts an integer that Integration Server retrieves from JSON content to either a Long or Integer Java wrapper type. If this parameter is set to true, Integration Server converts the JSON integer to a Long Java wrapper type. If this parameter is set to false, Integration Server converts the JSON integer to a Integer Java wrapper type. The default is true (Long).

Converts a real number that Integration Server retrieves from JSON content to either a Float or Double Java wrapper type. If this parameter is set to true, Integration Server converts the real number to a Double Java wrapper type. If this parameter is set to false, Integration Server converts the real number to a Float Java wrapper type. The default is true (Double).

Converts a real number that Integration Server retrieves from JSON content to String. If this parameter is set to true, Integration Server converts the real number to a String. If this parameter is set to false, Integration Server does not convert the real numbers to String instead, real numbers are converted to either Float or Double Java wrapper type depending on the values specified in decodeRealAsDouble. The default is false.

Controls how Integration Server parses JSON documents based on whether the documents have unique keys or duplicate keys. Integration Server can parse JSON documents faster when you set this parameter based on the nature of the documents you expect to receive. If you expect to process JSON documents that have unique keys or only a few duplicate keys, set this property to true (the default). If you expect to process JSON documents that have a lot of duplicate keys, set this property to false.

Specifies whether the output of JSONCoder.encode() is formatted with carriage returns and indentation to make the output easier to read. When Integration Server responds to a client request with JSON content, the format of that response is controlled by this property. If this parameter is set to true, Integration Server encodes JSON with carriage returns and indentation to ease readability. The default is false. For more information about JSONCoder, see webMethods Integration Server Java API Reference.

You can override this setting in individual requests that use the invoke, rest, or restv2 directives by including a query parameter of jsonPrettyPrint=true or jsonPrettyPrint=false in the URL used to invoke a service.

You can also set watt.server.json.prettyPrint to specify whether the pub.json:documentToJSONString service uses pretty print formatting in the jsonString output parameter. For more information about pub.json:documentToJSONString, see the webMethods Integration Server Built-In Services Reference.

Specifies whether or not the pub.json:documentToJSONString service encloses all generated JSON field names in double quotes. The JSON standard requires that field names be enclosed in double quotes. However, you may need the service to produce unquoted field names if the generated JSON text will be processed by an older JavaScript interpreter. Set this parameter to true instruct the pub.json:documentToJSONString service to enclose field names in quotes in the output JSON text. Set this parameter to false to instruct the service to omit the double quotes around field names in the generated JSON text. The default is true.

Specifies the license key for the server. There is no default.

Specifies whether Integration Server should close the TCP/IP connection and clean the LDAP context (the connectionHandle object) after processing a pub.client.ldap service request. When this property is set to true, Integration Server closes the connection and cleans the underlying LDAP context; Integration Server does not return the LDAP context to the pipeline. When this property is set to false (the default), Integration Server does not close the connection and returns the LDAP context to the pipeline.

For more information about the pub.client.ldap services, see webMethods Integration Server Built-In Services Reference.

Specifies the characters Integration Server can escape (using the \ character) in distinguished names presented to an LDAP server. By default, this property is set to null, meaning no characters are escaped.

Use this parameter if the distinguished names you are using include special characters that Integration Server needs to escape. For example, if your LDAP server maintains userids such as abc/def, specify the following:

If you need to escape the \ character, specify it twice:

Specifies the characters in LDAP distinguished names that Integration Server should not double-escape prior to their presentation to an LDAP server. To escape special characters in a distinguished name, you must precede the character with a backslash (\). By default, the following characters are never double-escaped, and should not be specified in watt.server.ldap.DNescapePairs:

, = + < > # ; / \

If the distinguished names in your LDAP server contain special characters other than those specified above, add them to watt.server.ldap.DNescapePairs so that Integration Server does not double-escape the characters. For example, do not add an equal sign (=) to watt.server.ldap.DNescapePairs, since this is never double-escaped by default. However, if the LDAP distinguished name contains an ampersand (&) and it should be double-escaped, add an ampersand character to watt.server.ldap.DNescapePairs as follows:

This property has no default value. If no value is supplied, no special characters beyond the set listed above are protected from double-escape. This property is not dynamic. Changes to its value go into effect after Integration Server is restarted.

Indicates whether Integration Server should ignore the first three forward slashes (/) in domain names, or to treat them as escape characters. If set to false (the default), Integration Server ignores the first three slashes in a domain name. Integration Server treats the slashes as part of the domain name, not as escape characters, regardless of the escape characters defined in the watt.server.ldap.DNescapeChars and watt.server.ldap.DNescapePairs server configuration parameters.

If set to true, Integration Server treats the forward slashes as escape characters and escapes domain names in accordance to the settings of watt.server.ldap.DNescapeChars and watt.server.ldap.DNescapePairs.

Specifies whether Integration Server should strip leading and trailing quotes from domain names presented to an LDAP server. When set to true (the default), Integration Server strips the quotes from domain names that contain special characters.

Specifies whether the Integration Server authenticates against the LDAP server. If your Integration Server uses a custom authentication module and you do not require users to be authenticated against the LDAP directory, set this property to true to prevent unnecessary requests to the LDAP server. The default is false.

Controls whether the Integration Server displays additional information returned from the LDAP server when an authentication error occurs. This information is available only if the LDAP server provides it. Active Directory is an LDAP server that provides this additional information. The default is false.

When set to false, an error message might look like this:

When set to true, the same error would be displayed like this:

For Active Directory users, the data code (data 52e above) contains the reason the authentication failed. You can convert the code to decimal and look it up on http://msdn.microsoft.com/library/en-us/debug/base/system_error_codes.asp to determine the problem.

Specifies LDAP environment properties that the Integration Server will pass directly to an LDAP implementation when initializing a JNDI context. It takes this form:

For example, if you are using a specialized JNDI provider other than the default, or if your LDAP directory requires a special JNDI property to be passed into the environment when a context is created, you could set the property customProperty to customValue:

There is no default.

Controls where Integration Server looks for LDAP group membership information. When set to true, the default, the Integration Server looks for group membership information in the group object. When set to false, the Integration Server looks for group membership information in the user object.

Specifies how many times Integration Server should automatically try to reconnect to an LDAP server after a network outage or LDAP server restart. If set to 0, the default, Integration Server will prompt the LDAP user for credentials rather than retrying the connection. If set to a positive integer, Integration Server will retry the connection the number of times specified. The default is 0.

Specifies how long Integration Server should wait before trying to reconnect to an LDAP server after a network outage or LDAP server restart. When set to 0, if there is a transient failure while communicating with LDAP, Integration Server will not try to reconnect to the LDAP server. If set to a positive integer, Integration Server will retry the connection the number of times specified in watt.server.ldap.retryCount and will wait the amount of time specified in watt.server.ldap.retryWait between retry attempts. The default is 0.

Specifies the number of licenses. The default is 1.

Specifies the number of entries that you can display in the Logs > logName page beyond which Integration Server Administrator displays an alert message. If the value entered in the Number of entries to display field in the Logs > logName page is more than the value specified for watt.server.log.alertMaxEntries, Integration Server Administrator displays a message informing that the number of requested entries exceeds the threshold and that displaying more entries might affect Integration Server performance. If no value is specified for watt.server.log.alertMaxEntries, Integration Server Administrator does not display any alert message.

Specifies the default number of log entries to be displayed in the log viewing utility. The default is 35 entries (the most recent entries). For complete information, see Changing the Display Permanently for All Logs.

Specifies the orphan loggers that you want to be adopted by the IS logging hierarchy. Some Integration Server logs become filled with debug messages even though the logging level is set to be higher than debug. This can happen when Integration Server has orphan loggers (loggers that are not part of the IS logging tree hierarchy) and a custom application configures the root logger of log4j. If there is not a custom configuration of log4j, the orphan loggers will inherit the logging levels specified in the IS logging tree hierarchy. However, if a custom application reconfigures the root logger in the log4j configuration file, the orphaned loggers inherit the logging level from the root logger. Consequently, if the log4j.rootLogger is set to DEBUG, the orphaned loggers will log at the Debug level.Use this parameter to prevent orphan loggers from logging at the modified log4j.rootLogger level. Use a comma to separate multiple orphan loggers. For example:

This is the default value.

Specifies whether the server is to queue log entries written by its facilities in memory, then use a background thread to write them to the server log. The default is true (queue log entries). For complete information, see the webMethods Audit Logging Guide.

Specifies the length of time (in seconds) that Integration Server Administrator refreshes the displayed server log. The default is 90 seconds. For complete information, see Changing the Display Permanently for All Logs.

Specifies the encoding that Integration Server uses for reading and writing text to the log files or to the console. The default is UTF-8.

Specifies the length of the log recycle interval (in milliseconds) for log entries. Starting with Integration Server 9.7, this server configuration parameter has been renamed watt.server.statsLogRotateInterval.

The watt.server.logRotateInterval parameter was removed from Integration Server after 8.2 SP2. When it was reintroduced for the following fixes, the scope of the parameter changed so that it affected only the stats.log:

If you migrate from Integration Server 9.6 or earlier to Integration Server 9.7 or higher, Integration Server:

Specifies the number of times a user can supply the wrong login credentials before Integration Server alerts the administrator and resets the count of login failures to 0. For example, if watt.server.loginFailureLimit is set to 5, when a user supplies the wrong login credentials for the sixth time, Integration Server sends an email alert to the administrator and resets the count of login failures to 0. The default value is 5.

Specifies whether the user who has connected to Integration Server through an FTP listener is to be placed in the default FTP root directory or the client user directory. When this property is set to false (or not specified), the user is logged into the FTP root directory. The user must then issue the cd command to access the client user directory. When this property is set to true, the user is logged into the client user directory. The default value is false.

The FTP root directory can be the default directory named userFtpRoot in your Integration Server home directory or a directory defined by the user using the watt.server.userFtpRootDir property.

Specifies the format of the date and timestamp to be used in audit log files (FailedAudit_*, WMERROR*, WMSESSION*, WMTXIN*, WMTXOUT*). The format you specify must adhere to the java.text.SimpleDateFormat class. If the watt.server.logs.dateStampFmt property is not set, Integration Server uses the default format, which is yyyy-MM-ddThh:mm:ss.SSSZ (for example, 2010-04-19T19:07:21.505Z).

Specifies the time zone to be used in audit log files (FailedAudit_*, WMERROR*, WMSESSION*, WMTXIN*, WMTXOUT*). The format you specify must adhere to the java.util.TimeZone class (for example, watt.server.logs.dateStampTimeZone=EST). If this property is not set, Integration Server uses local time zone hosting. For this property to take effect, the watt.server.logs.dateStampFmt must also be specified.

Specifies whether the pub.math:*Floats services return the exact result of an operation involving two floating point numbers, the result as calculated by the JVM, or the result based on a fixed number of decimal places.

Set this parameter to one of the following values:

Specifies a comma-separated list of directives used to detect Mediator requests. When Integration Server receives a request that uses the directives specified by the watt.server.mediator.directives server configuration parameter, Integration Server checks to see if the web service invoked by the request is a Mediator service. If the web service is a Mediator service, Integration Serverassigns the default user to the request. The default Mediator directives are "'ws,mediator".

Enables an extra level of verbose logging for webMethods messaging triggers that receive messages from Universal Messaging or through Digital Event Services. You can configure the additional logging globally or at the individual webMethods messaging trigger level.

The number of minutes a connection to a CentraSite registry can remain inactive before Integration Server closes it. Integration Server connects to one or more CentraSite registries to publish and retract metadata for your Integration Server assets. If no assets are published to or retracted from a CentraSite registry for a period of time, Integration Server closes the connection to that registry. The default period is 10 minutes.

Determines the global default behavior for how the pub.mime:createMimeData service handles header decoding. The property can have one of the following values:

Specifies the encoding the server is to use when reading and writing text to the network. This setting has no effect on text that is explicitly encoded in a particular encoding. The default is UTF-8. The encoding parameter in the pub.client:soapHTTP service, if set, overrides the watt.server.netEncoding setting. For more information about pub.client:soapHTTP, see webMethods Integration Server Built-In Services Reference.

Specifies whether Integration Server should create a new session object when executing the pub.client:http service. When this property is set to true, Integration Server ignores the values from the session object of the last invocation of pub.client:http and creates a new session object. When this property is set to false, Integration Server uses the values from the existing session object. The default value is false.

Specifies the URL to which the server redirects a request after three attempts to log on to the Integration Server Administrator have failed because the server cannot find the document the user is requesting. The default is for the server to display an HTML screen saying "No such object."

Specifies the URL to which the server is to redirect a request after three attempts to log on to the Integration Server Administrator have failed because the user does not have access to the requested document. The default is for the server to display an HTML screen saying "Access denied."

Specifies whether services are removed completely when they are deleted. When set to true, service node.ndf files will be renamed to node.bak when they are deleted. The default is false.

Specifies whether the dependency checking features are enabled or disabled. When set to true, the dependency checking features identify elements that will be affected by moving, renaming, or deleting another element. For optimization in a production environment, you might set this parameter to false. The default for this parameter is true.

Specifies whether Integration Server decodes and Designer displays non-ASCII Unicode characters in the body of a Java service. When you save Java services, Integration Server encodes non-ASCII Unicode characters as ASCII Unicode escape sequences. By default, Integration Server does not decode the escape sequences. Therefore, when Integration Server sends Java service code to Designer, escape sequences appear in Designer instead of the original Unicode characters. Set to true if you want Integration Server to decode the escape sequences so that Designer displays the original Unicode characters instead of the escape sequences. The default is false.

Indicates whether Integration Server should hide the WmRoot package from the Software AG Designer workspace. When set to true (the default), Designer does not display the WmRoot package in the workspace.

Specifies whether file locking is enabled on the Integration Server:

Indicates whether to suppress or continue logging of error messages related to registration of duplicate universal names for a document type.

When the same WSDL document is used to generate multiple consumer Web service descriptors and multiple WSDL first provider Web service descriptors, Integration Server creates multiple document types with the same explicit universal name. It is when loading a package containing these document types that Integration Server logs error messages specifying duplicate universal name registrations multiple times, which can clutter the log file.

Set the value of the parameter to false to suppress the logging of the error messages and true to resume the logging. The default value of this parameter is true.

Specifies the footer information that Integration Server displays on the OAuth approval page. There is no default.

Specifies the heading information that Integration Server displays on the OAuth approval page. The default is Resource access approval.

Specifies the URL of the image file that Integration Server displays on the OAuth approval page. Keep the following points in mind when specifying an image file:

The default is /WmPublic/images/fw_logo_sag.gif, which is 234x92 pixels.

Specifies the title that Integration Server displays on the OAuth approval page. The default is Access Approval.

Specifies the amount of time (in seconds) before the OAuth authorization code expires. A value of -1 indicates that the authorization code never expires. The maximum value is 2147483647. The default is 600.

The value of the watt.server.oauth.authCode.expirySeconds parameter is tied to the value of the Authorization code expiration interval field on the Security > OAuth > Edit OAuth Global Settings screen in Integration Server Administrator. Software AG recommends that you use Integration Server Administrator to specify the expiration time for the OAuth authorization code instead of using the watt.server.oauth.authCode.expirySeconds property. For more information about setting the expiration time for the OAuth authorization code, see Configuring OAuth.

Specifies the alias of the remote server that Integration Server uses as an authorization server. The value should match the Alias field on the Settings > Remote Servers page of Integration Server Administrator. For example, local.

The value of the watt.server.oauth.authServer.alias parameter is tied to the value of the Authorization server field on the Security > OAuth > Edit OAuth Global Settings screen in Integration Server Administrator. Software AG recommends that you use Integration Server Administrator to specify the remote server alias to use as an authorization server instead of using the watt.server.oauth.authServer.alias property. For more information about specifying the remote server alias, see Configuring OAuth.

When set to true, OAuth and OpenID errors that are returned to client applications and to end users appear in the HTTP response header with a header attribute name of X-OAuth-Error. For most OAuth and OpenID errors, Integration Server returns a status code in the range of 400 - 599 and the error message is returned in the body of the HTTP response. Some browsers do not display the response body when the status code is not successful (200 - 299). Problems with your applications that use OAuth or OpenID can be easier to troubleshoot when the error message is in the response header. When the Server logging facility "0038 HTTP Header" is set to TRACE, the response header is visible in the server log. If watt.server.oauth.custom.responseHeader is true, OAuth and OpenID error messages will appear as X-OAuth-Error response header attributes in the server log.

The default value for watt.server.oauth.custom.responseHeader is false.

Indicates whether Integration Server requires that client applications use HTTPS to access the pub.oauth* services. If you set the value of this property to false, Integration Server allows client applications to use HTTP to access the pub.oauth* services. The default is true.

If you set the value of this property to true and the client application accesses any of the pub.oauth services over HTTP, Integration Server issues an HTTP 400 error response to the client and writes a service exception to the error log.

The value of the watt.server.oauth.requireHTTPS parameter is tied to the value of the Require HTTPS field in the Security > OAuth > Edit OAuth Global Settings page of the Integration Server Administrator. Software AG recommends that you use Integration Server Administrator to indicate whether Integration Server requires HTTPS for applications to access OAuth services instead of using watt.server.oauth.requireHTTPS. For more information about requiring HTTPS for accessing OAuth services, see Configuring OAuth.

For more information about the pub.oauth services, see webMethods Integration Server Built-In Services Reference.

Indicates whether Integration Server requires that client applications use HTTP POST method to access the pub.oauth* services. If you set the value of this property to false, Integration Server allows client applications to use the HTTP GET method to access the pub.oauth* services. The default is true.

If you set the value of this property to true and the client application accesses any of the pub.oauth services using an HTTP method other than POST, Integration Server issues an HTTP 400 error response to the client and writes a service exception to the error log.

Specifies the amount of time (in seconds) that access tokens are valid before expiring. A value of -1 indicates that authorization tokens never expire. The maximum value is 2147483647. The default is 3600.

The value of the watt.server.oauth.token.defaultExpirySeconds parameter is tied to the value of the Access token expiration interval field in the Security > OAuth > Edit OAuth Global Settings page of the Integration Server Administrator. Software AG recommends that you use Integration Server Administrator to set the expiration time for access tokens instead of using watt.server.oauth.token.defaultExpirySeconds. For more information about the Access token expiration interval field, see Configuring OAuth.

Specifies the maximum number of threads that you want Integration Server to use when loading IS packages at startup. The threads are from a thread pool that Integration Server uses only at startup and specifically for package loading. If you want Integration Server to load packages sequentially, set the value to 1. If you want Integration Server to load packages in parallel, set the value to 2 or higher. It is recommended that you do not exceed 10. The default value is 6.

Specifies whether, at package load time, Integration Server loads the external resources for a consumer web service descriptor or a WSDL first provider web descriptor created on a pre-8.2 version of Integration Server with the Pre-8.2 compatibility mode property set to true.

When this parameter is set to true, Integration Server resolves all the import and include statements in the source WSDL document and related XML Schema definition files for consumer web service descriptors or WSDL first provider web service descriptors at the package load time.

When this parameter is set to false, Integration Server skips loading the external resources contained in the source WSDL document used to create the web service descriptor. In some environments, setting this parameter to false may speed up the loading of web service descriptors. The default is true.

Specifies the IP address or domain name of a hub server. This setting allows the partner server to issue a remote invoke request to a remote Integration Server. Integration Server will ignore a port number if you specify one as part of an IP address.

Specifies the minimum number of digits a password must contain for non-Administrator users. When a non-Administrator user changes a password, he or she must create a password containing at least the number of digits specified by this parameter. If the minimum number of digits is not met, Integration Server sends a warning message to the Administrator user. The default is 1.

Specifies the minimum number of characters a password must contain for non-Administrator users. The character length includes upper and lower case alphabetic characters, digits (0-9), and special characters combined. When a non-Administrator user changes a password, he or she must create a password containing at least the number of characters specified by this parameter. If the minimum length is not met, Integration Server sends a warning message to the Administrator user. The default is 8.

Specifies the minimum number of lowercase alphabetic characters a password must contain for non-Administrator users. When a non-Administrator user changes a password, he or she must create a password containing at least the number of lowercase characters specified by this parameter. If the minimum is not met, Integration Server sends a warning message to the administrator user. The default is 2.

Specifies the minimum number of special characters, such as asterisk (*), period(.), and question mark(?), a password must contain for non-Administrator users. When a non-Administrator user changes a password, he or she must create a password containing at least the number of special characters specified by this parameter. If the minimum is not met, Integration Server sends a warning message to the Administrator user. The default is 2. The use of special characters is regulated by the following restrictions:

Use the watt.server.illegalUserChars configuration property to restrict the use of additional characters.

Specifies the minimum number of uppercase alphabetic characters a password must contain for non-Administrator users. When a non-Administrator user changes a password, he or she must create a password containing at least the number of uppercase characters specified by this parameter. If the minimum is not met, Integration Server sends a warning message to the Administrator user.

Specifies whether or not to enforce the password restrictions when setting passwords for administrator or non-administrator users. When set to strict, the password restrictions are enforced and when set to lax, the password restrictions are not enforced. The default is lax.

Specifies whether to globally enable or disable the Pipeline Debug feature. When set to true, Integration Server checks the Pipeline Debug values for the service at run time. You can view and set the Pipeline Debug values in the Properties view in Designer. When set to false, Integration Server ignores the Pipeline Debug options set for the service in Designer. The default is true.

Enable this property in development environments where testing and debugging is performed. In a production environment, however, disabling this property is recommended.

Specifies the port number of the Integration Server's primary port. The default is 5555.

Specifies the size of the port queue for HTTP and HTTPS ports. The port queue is the number of outstanding inbound connections that are queued in the TCP/IP stack. The default is 65534. If your server runs on AS/400, set this number to 511.

Specifies whether Integration Server should reject locally published documents when the queue for the subscribing trigger is at maximum capacity.

When this parameter is set to true, before placing a locally published document into a subscribing trigger's queue, Integration Server first checks the trigger's queue size. If the queue already contains the maximum number of documents allowed by the trigger's Capacity property, Integration Server rejects the locally published document for that trigger queue only.

When this parameter is set to false, Integration Server continues to place locally published documents into a subscribing trigger's queue even when the queue is at capacity. This is the default.

Specifies whether Integration Server uses outbound client-side queuing if documents are published when the Broker is unavailable. Set this parameter to always to send published documents to the outbound document store when the Broker is not available. Set this parameter to never to instruct the publishing service to throw a ServiceException when the Broker is not available. The default is always.

If client-side queuing is enabled, this parameter specifies whether Integration Server should empty the outbound document store in publication order or in parallel with newly published documents. When this parameter is set to true, Integration Server sends all newly published documents (guaranteed and volatile) to the outbound document store until the outbound store has been emptied. This allows the Integration Server to maintain publication order. When this parameter is set to false, the outbound store is emptied while new documents are being published to the Broker. The default is true.

Specifies whether Integration Server should bypass encoding that is normally performed when documents are published to the Broker. If this property is set to true, Integration Server checks the pipeline for an object called $brokerEvent. If the object is found and is of type BrokerEvent, Integration Server sends its value to the Broker and no additional encoding is performed. Set this parameter to true if Integration Server is sending native Broker events. The default is false.

For more information about publishing native Broker events, see the Publish-Subscribe Developer’s Guide.

Specifies whether Integration Server validates published documents. Set this parameter to one of the following values:

For information about handling native Broker events and specifying validation for an individual publishable document type, see the Publish-Subscribe Developer’s Guide.

Specifies the size of the buffer that Integration Server uses to write an XML string when converting a document (IData) to an XML string. Increase the buffer size if the majority of the created XML strings will be greater than 4 KB. Decrease the buffer size if the majority of the created XML strings will be small documents less than 4 KB in size. The default size is 4 KB.

Indicates if, during a remote service invocation, Integration Server queries the remote server for the CSRF token for the current session and then includes the token in the service request. If an Integration Server uses Cross-Site Request Forgery (CSRF) guard, requests sent to the server must include a CSRF token. If the request does not include a CSRF token, the server rejects the request. When an Integration Server performs a remote invoke to execute a service on another Integration Server that uses CSRF guard, the request needs to include the CSRF token. To ensure that the request includes a CSRF token, the requesting Integration Server obtains the CSRF token for the current session from the remote Integration Server. The requesting Integration Server then modifies the request to include the CSRF token. However, this is only necessary if the remote Integration Server uses CSRF guard. Set the watt.server.remoteInvoke.queryCSRFToken to true if remote Integration Servers use CSRF guard and you want the requesting Integration Server to query for the current CSRF token and include that token in the request. Set to false if the remote Integration Servers does not use CSRF guard. The default is true.

Specifies whether the Integration Server requests a digital certificate from clients that connect to it through SSL. Set this parameter to true if you want the server to request certificates. Set it to false if you do not want the server to request certificates. The default is false.

Specifies an alternative word to use for the rest directive in URLs that access resources on Integration Server. By default, this parameter is set as watt.server.RESTDirective=rest, which means users must specify the rest directive as rest (for example, GET http://host:port/rest/resource/resourceID). To allow users to specify the rest directive as either rest or an alternative word, set this parameter to the alternative word. For example, to allow users to specify the rest directive as either rest or process, (GET http://host:port/rest/resource/resourceID) or GET http://host:port/process/resource/resourceID), set this parameter as watt.server.RESTDirective=process.

Specifies an alternative word to use for the restv2 directive in URLs that access resources on Integration Server. By default, this parameter is set as watt.server.RESTDirective=restv2, which means users must specify the rest directive as restv2 (for example, GET http://host:port/restv2/resource/resourceID). To allow users to specify the rest directive as either restv2 or an alternative word, set this parameter to the alternative word. For example, to allow users to specify the directive as either restv2 or process, (GET http://host:port/restv2/resource/resourceID) or GET http://host:port/process/resource/resourceID), set this parameter as watt.server.RESTDirective.V2=process.

Indicates whether the HTTP response from Integration Server to a client application in the case of an error situation includes the Integration Server error code in the header and the body of the response.

If you set the value of this parameter to false, the HTTP response during error situations includes the error message text without the Integration Server error code in both the header and the body of the response. If you set the value to true, the HTTP response during error situations includes the Integration Server error code and the corresponding error message text in the header and body of the response. The default value of the parameter is true.

For webMethods Enterprise Gateway only. Specifies whether an Enterprise Gateway Server is to perform client authentication itself in addition to passing authentication information to the Internal Server for processing. The default is false. If this property is set to true, Enterprise Gateway Server will reject all anonymous requests (no certificate and no username/password supplied), even if the request is for an unprotected service on the Internal Server. See Configuring webMethods Enterprise Gateway for more information.

For webMethods Enterprise Gateway configuration only. Set this value on the Internal Server to specify the time (in seconds) the Internal Server will wait before closing an unresponsive connection to the Enterprise Gateway Server. The default is 0, which means the Internal Server will not time out (a timeout period of infinity).

Specifies the length of time, in milliseconds, that Enterprise Gateway Server allows a client request to wait for a connection to the Internal Server before terminating the request with an HTTP 500 Internal Server Error. If a connection to the Internal Server becomes available within the specified timeout period, Enterprise Gateway Server forwards the request to the Internal Server. If a connection does not become available before the timeout elapses, Enterprise Gateway Server returns a HTTP 500-Internal Server Error to the requesting client and writes the following message to the error log:

"Enterprise Gateway port {port_number} is unable to forward the request to Internal Server because there are no Internal Server connections available."

The default value of this parameter is 0 which means that the client request waits indefinitely for a connection to the Internal Server.

Specifies whether or not scheduled tasks that have expired should be automatically deleted. When set to true, Integration Server deletes expired tasks when they expire. Set this parameter to false if you want Integration Server to wait until the next server restart to delete expired tasks. The default is true.

Specifies whether Integration Server creates or executes a scheduled task if the scheduled service has a broken reference. Set the property to true to indicate that Integration Server ignores broken references for the scheduled service when executing a scheduled task. Set it to false to indicate that Integration Server should not execute a scheduled task if the scheduled service has one or more broken references. The default is false.

Specifies a unique logical name to identify Integration Server instances in a cluster hosted on a single machine. By default, Integration Server uses the host name to identify itself while scheduling tasks. However, when a cluster of Integration Servers are hosted on a single machine, the host name itself cannot uniquely identify the individual Integration Server instances. In such cases, use the watt.server.scheduler.logical.hostname property to specify a unique logical name to identify individual Integration Server instances.

The default value for this parameter is the host name.

Keep the following points in mind when setting the watt.server.scheduler.logical.hostname property:

This property is also useful when Integration Server is installed on a virtual server whose host name or IP address might change over time. You can use watt.server.scheduler.logical.hostname to provide a fixed value that identifies each server in a cluster.

Maximum time in seconds Integration Server waits between queries of the task queue. The server periodically checks the queue for tasks that are scheduled to run. If there are no tasks waiting to run, the server waits the maxWait time before checking the queue again. If there are tasks waiting to run, the server checks again at the task's schedule execution time, or after the maxWait time, whichever is earlier. For example, if the pending task is due to execute in 30 seconds and the maxWait time is 60, the server will check the queue again in 30 seconds. The default is 60.

If you run a cluster of Integration Servers and schedule a task to run on all servers in the cluster, you might notice tasks starting at different times on the different servers if the servers have different settings for this property. For this reason, if you are running in a clustered environment, all the servers in your cluster should have the same settings for this property. See the webMethods Integration Server Clustering Guide for more information about configuring Integration Servers in a cluster.

Percentage of Integration Server threads the scheduler process is permitted to use. The default is 75%.

Specifies the number of server log files that Integration Server keeps on the file system, including the current server log file. When Integration Server reaches the limit for the number of server log files, Integration Server deletes the oldest archived server log file each time Integration Server rotates the server log. If you set watt.server.log.filesToKeep to 1, Integration Server keeps the current server.log file and no previous server.log files. When Integration Server rotates the server.log, Integration Server does not create an archive file for the previous server log. If you set watt.server.log.filesToKeep to 0, or any value less than 1, Integration Server keeps an unlimited number of server log files.

The default value of watt.server.log.filesToKeep is -1, indicating that there is no limit to the number of server log files that Integration Server maintains.

For more information about setting the maximum number of server log files that Integration Server keeps, see Setting Up the Server Log.

Specifies the file size at which Integration Server rolls over the server.log file. Set this property to N[KB|MB|GB], where N is any valid integer. The minimum size at which Integration Server rotates the server.log file is 33KB. If you use KB as the unit of measure, you must set N to a value greater than or equal to 33. If you do not specify a unit of measure, Integration Server treats the supplied N value as bytes. In this case, N must be greater than or equal to 32768 to take effect. Do not include any spaces between the integer and the unit of measure.

There is no default value for this parameter. That is, by default, the parameter has no value. If no value is specified for watt.server.serverlogRotateSize, Integration Server rotates the server.log file at midnight only.

If an invalid value is specified, Integration Server resets the parameter to -1. Note that a value of -1 results in the same behavior as specifying no value for the parameter.

For more information about the server.log, see Setting Up the Server Log.

Controls the number of entries allowed in the server log queue. This property is related to the watt.server.log.queued property, which controls whether the server is to write entries directly to the server log, or queue them in memory first and then use a background thread to write them to the server log. If your configuration has the watt.server.log.queued property set to true and you notice that expected server log entries are not included in the log, try increasing the queue size. For more information about the server log and the server log queue, see Specifying Whether to Queue Server Log Entries. The default queue size is 8192.

This is an internal property. Do not modify.

Controls whether Integration Server initializes Java services during startup. When set to true (the default), Integration Server does not initialize Java Services until they are referenced during runtime. This can increase performance if the server initializes a lot of Java Services at start up.

Specifies the email address to which Integration Server sends messages about service failures. There is no default.

When you specify an email address on this parameter, Integration Server creates a simple scheduled task to perform the notification. This task requires a thread, which Integration Server takes from the cronjob-based thread pool. See the watt.server.cron.maxThreads and watt.server.cron.minThreads parameters for more information about this thread pool.

Specifies the name of the public cache to use for service results caching. If no value is specified for the watt.server.serviceResults.cache parameter, Integration Server uses the ServiceResults cache in the cache manager specified in the watt.server.serviceResults.cacheManager parameter as the service results cache. If the cache manager in the watt.server.serviceResults.cacheManager parameter does not contain a cache named ServiceResults, Integration Server throws an error at start up and does not cache service results.

Specifies the name of the public cache manager that contains the public cache to use for service results caching. If no value is specified for this parameter, Integration Server uses the SoftwareAG.IS.Services system cache manager as the service results cache manager. If the SoftwareAG.IS.Services system cache does not contain a cache with a name that matches the value of the watt.server.serviceResults cache, Integration Server throws an error at startup and does not cache service results.

Specifies how the cache should copy elements that it returns. The default value true returns the results by value, while the value false returns results by reference.

Specifies how the cache should copy elements that it writes. The default value true returns the results by value, while the value false returns results by reference.

Specifies the interval, measured in seconds, that elapses before Integration Server Administrator refreshes the data on the Server > Statistics page. The default is 90 seconds. The change to the parameter takes effect the next time the Server > Statistic page is reloaded.

Specifies whether the default locale for the pub.date* services is the server locale or the locale from the session used by the client that invoked the service. When set to true, when executing a pub.date* service for which a locale input parameter value is not specified, Integration Server uses the server locale as the value of the locale parameter. When set to false, when executing a pub.date* service for which a locale input parameter value is not specified, Integration Server uses the locale from the session used by the client that invoked the service. The default is false.

Controls whether the stateful session limit feature is enabled. When this property is set to true, Integration Server allows stateful sessions to be created as needed until it reaches the maximum allowed, which is specified by the watt.server.session.stateful.max property. You can view statistics for stateful sessions on the Server > Statistics screen in Integration Server Administrator.

Specifies the number of concurrent stateful sessions allowed on the Integration Server. If a user attempts to access the server and execute a stateful service while the maximum number of stateful sessions are in use, the server rejects the request and returns an error to the user.

The value for watt.server.session.stateful.max must be a positive integer. If a value is not specified or the watt.server.session.stateful.enableLimit property is set to false, the maximum number of concurrent sessions is defined by your Integration Server license.

Specifies the threshold at which Integration Server starts to warn of insufficient available stateful sessions. When the percentage of available stateful sessions is equal to or less than the value of this property, Integration Server generates a server log message stating:

The default is 25%.

Specifies the order in which the pub.flow:setResponse service looks for and uses the deprecated input parameters when neither of the input parameters responseString or responseBytes are provided.

When set to true, the pub.flow:setResponse service follows a precedence order similar to what was available in Integration Server 7.1x and 8.0x. Specifically, the service looks for the deprecated parameters in the following order and uses the value of the first parameter that it finds: response, string, bytes

When set to false, the pub.flow:setResponseservice follows a precedence order similar to what was available in Integration Server 8.2 and later. Specifically, the service looks for the deprecated parameters in the following order and uses the value of the first parameter that it finds: string, bytes, response

The default is false.

Specifies the format of date to be used in the SFTP client public services, specifically the pub.client.sftp* services in the WmPublic package. To specify the date format to use, you can use any format that is supported by the Java class java.text.SimpleDateFormat. For example, to display the date with the format 08-12-02 14:44:33:1235, specify dd-MM-yy HH:mm:ss:SSSS. The default format for watt.server.sftp.dateStampFmt property is yyyy-MM-dd HH:mm:ss z.

Specifies the SMTP server to use for server error logging and service error email notification. There is no default.

Specifies the number of the listening port on the SMTP server to which the Integration Server is to send server error logging and service error email notification. The default is 25.

Specifies the type of SSL encryption that Integration Server uses when communicating with an SMTP server.

Set this property to any one of the following values:

Specifies the alias for the truststore that contains the list of certificates that Integration Server uses to validate the trust relationship between Integration Server and the SMTP server. If you do not specify a truststore alias, the default truststore alias specified in the watt.security.trustStoreAlias property will be used. For more information about truststore alias, see Creating Truststore Aliases.

Specifies whether Integration Server should create an empty header entry in the SOAP message created by executing the pub.soap.utils:createSoapData or pub.soap.utils:stringToSoapData services. When this property is set to true, Integration Server creates an empty header in the SOAP message. When this property is set to false, Integration Server does not create a header entry in the SOAP message. The default is true.

The addEmptyHeader parameter in the pub.soap.utils:createSoapData or pub.soap.utils:stringToSoapData services, if set, overrides the watt.server.SOAP.addEmptyHeader setting.

For more information about pub.soap.utils:createSoapData and pub.soap.utils:stringToSoapData services, see webMethods Integration Server Built-In Services Reference.

Specifies whether the XML node added by pub.utils:addBodyEntry, pub.utils:addHeaderEntry, pub.utils:addTrailer will be completely loaded before adding to the SOAP message. When set to true, Integration Server loads the entire XML node. When set to false, Integration Server does not completely load the XML node before adding it to the service. The default is true.

Specifies how Integration Server returns the response from a web service invocation when it is acting as a client and the web service results in a plain text HTTP response. This parameter applies only when the web service connector was created using:

When the watt.server.soap.convertPlainTextHTTPResponseIntoSOAPFault parameter is set to true (the default), Integration Server converts the plain text HTTP response and returns the information from the HTTP response within web service connector's output parameters.

Having the plain text HTTP response converted and returned in the web service connector’s output parameter can be helpful because it might contain the cause of the exception.

If you set the parameter to false, when the web service results in a plain text HTTP response, Integration Server throws an exception indicating that an invalid SOAP envelope is received.

Specifies whether Integration Server recognizes document types that have defined XML namespace URIs but do not have prefixes associated with each namespace. By default, in Integration Server version 8.2 SP2 and higher, if document types that have a defined XML namespace URI but do not have a prefix associated with each namespace are specified as inputs to services, the SOAP processor fails to recognize the document types at run time. If the watt.server.soap.decodeElementWithPrefix property is set to true, Integration Server recognizes the document types that have defined XML namespaces but do not have prefixes associated with each namespace.

The default is false.

The watt.server.soap.decodeElementWithPrefix server configuration parameter value affects how Integration Server decodes inbound SOAP messages for web service descriptors created on Integration Server version 7.1.x. Specifically, the parameter affects how Integration Server decodes SOAP response messages received by a 7.1.x web service connector and SOAP request messages received by a 7.1.x web service provider.

The watt.server.soap.decodeElementWithPrefix server configuration parameter also determines whether or not the pub.xml.xmlNodeToDocument service considers namespace and/or prefix declarations when decoding namespace qualified elements to corresponding fields in an IS document type.

Specifies the default provider web service endpoint alias for the HTTP protocol. If the value of this parameter is empty, there is no default provider web service endpoint alias for HTTP.

There is no default value for this parameter.

The watt.server.SOAP.default.endpointHTTP parameter displays the value specified in the HTTP parameter on the Settings > Web Services > Set Default Provider Endpoint Aliases screen in Integration Server Administrator. Software AG recommends that you specify the default provider endpoint alias using the HTTP parameter on the Settings > Web Services > Set Default Provider Endpoint Aliases screen instead of by changing the value of the watt.server.SOAP.default.endpointHTTP parameter. For more information about setting a default provider endpoint alias, see Setting a Default Endpoint Alias for Provider Web Service Descriptors.

Specifies the default provider web service endpoint alias for the HTTPS protocol. If the value of this parameter is empty, there is no default provider web service endpoint alias for HTTPS.

There is no default value for this parameter.

The watt.server.SOAP.default.endpointHTTPS parameter displays the value specified in the HTTPS parameter on the Settings > Web Services > Set Default Provider Endpoint Aliases screen in Integration Server Administrator. Software AG recommends that you specify the default provider endpoint alias using the HTTPS parameter on the Settings > Web Services > Set Default Provider Endpoint Aliases screen instead of by changing the value of the watt.server.SOAP.default.endpointHTTPS parameter. For more information about setting a default provider endpoint alias, see Setting a Default Endpoint Alias for Provider Web Service Descriptors.

Specifies the default protocol that Integration Server uses for new SOAP messages. Specify SOAP 1.1 Protocol or SOAP 1.2 Protocol. The default is SOAP 1.1 Protocol.

Specifies a different word to use for the SOAP directive in URLs that route requests to the Integration Server SOAP handler. By default, this parameter is set as watt.server.SOAP.directory=soap, which means users must specify the SOAP directive as soap (http://host:port/soap). To allow users to specify the SOAP directive as a different word instead, set this parameter to that word. For example, to allow users to specify the SOAP directive as endpoint, (http://host:port/endpoint), set this parameter as watt.server.SOAP.directive=endpoint.

Indicates where the xsi:type will appear as an attribute for an element in a SOAP message that specifies RPC/Encoded. A value of true indicates that Integration Server includes the xsi:type attribute for an element. False indicates that the xsi:type attribute will be omitted. The default is true. Software AG recommends using a value of true for this parameter.

Indicates whether Integration Server should include the xsi:type attribute and its value for an element of xsd:anyType in SOAP requests and responses. When set to false, Integration Server omits the xsi:type attribute and its value for an element of xsd:anyType in SOAP requests and responses. When set to true, Integration Server includes the xsi:type attribute and its value for an element of xsd:anyType in SOAP requests and responses. The default is true.

Specifies whether or not Integration Server generates an xsi:nil attribute for an element in a SOAP message. When set to true, Integration Server generates an xsi:nil attribute for an element that is nillable (the Allow null property for the corresponding field is set to true) and the field is null at run time. When watt.server.SOAP.generateNilTags is set to false, Integration Server omits the xsi:nil attribute for an element even if the corresponding field is nillable and the field is null at run time. The default is true.

Specifies whether or not a SOAP message generated by Integration Server includes empty element tags for required parameters for which a value was not supplied at run time. When set to true, Integration Server generates empty element tags for required parameters for which a value is not specified. When watt.server.SOAP.generateRequiredTags is set to false, Integration Server omits empty element tags for required parameters for which a value is not specified. The default is true.

Hides the endpoint reference host name and IP address details in the SOAP fault. When this parameter is set to true, Integration Server replaces the host name and IP address with *:* in the SOAP fault. When this parameter is set to false, Integration Server includes the host name and IP address details of the endpoint reference in the SOAP fault. The default is false.

Configures the Axis stack to use an alternate multipart writer implementation based on the JavaMail API. Changing the multipart writer implementation used by Axis allows Mediator to handle non-ASCII characters in SOAP XML requests with multipart attachments. Set to true to configure the AXIS stack to use the alternate multipart writer implementation. The default value is false.

Determines whether missing required headers in a SOAP response results in an error. When set to true, a SOAP response that does not contain a required header will not result in an error. When set to false, a SOAP response that does not contain a required header results in an error. The default is false.

Note that all headers in a web service descriptor, whether generated from the original WSDL document or added to the web service descriptor, are treated as required. This is an application of the WS-I basic profile rules declaring that all headers in a WSDL be treated as required. Prior to Integration Server version 9.0, when processing a SOAP response received by a web service descriptor, Integration Server did not properly validate that all of the SOAP headers were present. As a result, Integration Server did not throw an error when a SOAP response was missing a SOAP header. Beginning in Integration Server version 9.0, Integration Server properly validates SOAP responses for required headers. If a required header is not present, Integration Server throws the following error: “[ISS.0088.9443] One or more required Headers <headerName> are not present in the SOAP response.” While failure when a required header is missing is the correct behavior, Integration Server provides a configuration property to control whether missing required headers in a SOAP response results in an error. This can be useful in migration situations.

Specifies the absolute path to the hard disk drive space that Integration Server uses to temporarily store inbound SOAP messages when performing MTOM streaming. This parameter takes effect only when MTOM streaming is enabled (i.e., watt.server.SOAP.MTOMStreaming.enable is set to true).

You can specify a directory on the same machine as the Integration Server or in any other location accessible to Integration Server, such as a mapped logical drive or network directory. The default value is Integration Server_directory \instances\instance_name\temp\mtom\cached files.

Indicates whether MTOM streaming is enabled for inbound SOAP messages and whether HTTP chunking is enabled for outbound requests. Set this property to true to enable MTOM streaming for inbound SOAP messages and HTTP chunking for outbound requests. Set this property to false to disable MTOM streaming and HTTP chunking. The default is false.

Specifies the maximum number of bytes for Integration Server to handle an inbound MTOM attachment field as an in-memory ByteStream. Integration Server writes an inbound MTOM attachment field exceeding this size to a temporary disk file and processes the inbound MTOM Streams as a FileStream. This parameter takes effect only when MTOM streaming is enabled (watt.server.SOAP.MTOMStreaming.enable is set to true). The default is 4000 bytes.

The watt.server.SOAP.MTOMStreaming.cachedFiles.location value determines the location of the temporary disk files.

Specifies the field size, in kilobytes, that determines whether Integration Server handles base64binary encoded data in an outbound SOAP request as a MIME attachment or whether it sends it inline in the SOAP message. If the web service descriptor for the SOAP message enables attachments for the SOAP request, Integration Server passes as MIME attachments any base64 fields in a SOAP message that are larger than the threshold. The default is 0.

For a web service provider that was created in an Integration Server release earlier than 8.2.2 and for which the Pre-8.2 compatibility mode property is set to true, specifies whether to emulate pre-8.2 behavior for process SOAP requests. In Integration Server 7.1.3, Integration Server allowed web service providers to process SOAP requests with a SOAP version that did not match the SOAP version that was declared in the WSDL binding. When set to true, this property provides backward compatibility so that consumers do not have to update their SOAP requests.

When set to false, Integration Server uses stricter validation that does not allow processing when this mismatch exists. The default value is false.

Changes to this property take effect immediately.

Specifies the length of time, in seconds, Integration Server will wait for the SOAP response from the server hosting the remote procedure. If Integration Server does not receive a response in the allotted time, it terminates the request. The default value is -1, which indicates that Integration Server will use the value set for the watt.net.timeout property.

Specifies how Integration Server declares XML namespaces in a SOAP response. When the watt.server.SOAP.setNamespaceURIsToRoot property is set to true, Integration Server declares the namespace and prefix once at the root element of the SOAP response and then uses the prefix for each element in the response. When set to false, Integration Server declares the namespace the way it is defined in the original document, either defining each element explicitly with the full namespace or declaring the namespace and prefix just once at the root element. The default value for this property is false.

Specifies the custom SOAP handlers that expect stream inputs. Enter the SOAP handlers as a semi-colon (;) separated list. There is no default.

Indicates whether or not Integration Server, when decoding a SOAP message, generates an @xsi:nil field for an element for which the xsi:nil attribute is set to true. When set to true, Integration Server treats an element that carries the xsi:nil attribute as a null value and does not create an @xsi:nil attribute for the element. When this parameter is set to false, Integration Server generates an @xsi:nil field for an element that carries the xsi:nil=true attribute. This configuration parameter affects all web services running on Integration Server. The default is true.

For elements that appear in multiple places in a SOAP message, specifies whether Integration Server serializes each occurrence of the element or serializes it in on only one place and uses the href attribute in the other locations. When set to true, Integration Server serializes one location and uses the href attribute in other locations. This parameter applies to RPC/Encoded web services only. The default is true.

Specifies how Integration Server decodes an xsd:anyType element with simple content in SOAP responses. When set to false, Integration Server decodes xsd:anyType elements with simple content into an IData with an @xsi:type field to retain the xsi:type value and a *body field to contain the element value. This is the default behavior.

When the watt.server.SOAP.useStringforAnyTypewithSimpleValue server configuration parameter is set to true, Integration Server decodes xsd:anyType elements with simple content into a String type field that contains the element value. The element's xsi:type information will be gone. You do not have to restart Integration Server for the change to take effect.

Enables or disables SOAP response validation. When set to true, Integration Server validates the SOAP response received by a web service connector. When set to false, Integration Server does not validate the received SOAP response. The default is true.

When Integration Server acts as the web service provider, indicates whether Integration Server validates inbound SOAP requests and outbound SOAP responses. When set to true, Integration Server validates inbound SOAP requests and outbound SOAP responses against the SOAP schema. Be aware that the validation process checks only that the message envelope is structured correctly. For example, Integration Server checks that the message has at least one body element and there is at most one header element. Integration Server does not validate any of the data carried by the message. The default is true.

If you are operating in a production environment where the validity of the messages submitted to the server is assured, you might set watt.server.SOAP.validateSOAPMessage to false to optimize performance.

When creating a web service descriptor from a WSDL document, indicates whether Integration Server should treat message parts that are defined by the type attribute instead of the element attribute as a warning and not an error. Set this parameter to true to indicate that Integration Server should return a warning and allow the web service descriptor to be created. Set this parameter to false to indicate that Integration Server should return an error and not allow the web service descriptor to be created. The default is false.

Specifies the default message type for web service request messages sent using SOAP over JMS. Set this parameter to "BytesMessage" to send a message whose body contains a stream of uninterrupted bytes. Set this parameter to "TextMessage" to send a message whose body contains a Java string. BytesMessage is considered to be a more efficient way of sending JMS messages. However, you may want to set the parameter to TextMessage for debugging purposes because the resulting messages will be in a human-readable format. Keep in mind that the message type of the request message determines the message type of the response message. The default is BytesMessage.

Specifies the number of seconds that Integration Server waits for a response to a SOAP request sent using SOAP over JMS. This value must be an integer greater than or equal to zero. A value of 0 indicates that Integration Server will wait indefinitely for a response. The default is 10 seconds.

Indicates whether Integration Server should check SOAP headers for SOAP RPC requests. The default is true.

Indicates whether Integration Server should differentiate identically named arrays in the SOAP response for a SOAP/RPC web service. When set to true, Integration Server appends a number to the xsi:type value to distinguish between identically named array elements in the SOAP response, for example elementName and elementName1. When set to false, Integration Server does not differentiate identically named arrays in the SOAP response. The default is true.

Instructs Integration Server to use a second type definition when creating the SOAP response for a service whose input or output signatures contain identically named variables of different types. When creating a WSDL from a provider web service descriptor that contains a service with identically named fields of different types, Integration Server renames the second instance of the field type in the WSDL. At run time, for RPC-Encoded SOAP binding, Integration Server encodes the types in the SOAP response. When this property is set to true, the SOAP response refers to the renamed type definition. When set to false, the SOAP response refers to the original type definition instead of the renamed one. The default is false. This property is applicable to RPC-Encoded SOAP binding only.

Name of the keystore alias for the Integration Server keystore that contains the information needed to establish an SSL connection with an SSL-enabled external server. There is no default value for this parameter. For more information about storing keystore information for an SSL connection to an external server, see Storing SSL Information for the Integration Server JVM in a Secure Manner.

Name of the truststore alias for the Integration Server truststore that contains the information needed to establish an SSL connection an SSL-enabled external server. There is no default value for this parameter. For more information about storing truststore information for an SSL connection to a an external server, see Storing SSL Information for the Integration Server JVM in a Secure Manner.

Specifies the time period (in seconds) for which performance metrics are averaged. The default is 10.

Specifies the name of the file to receive statistics. The file contains the data that appears on the Server > Statistics page. The default file name is logs\stats.log.

Specifies the number of stats.log files that Integration Server keeps on the file system, including the current log file. When Integration Server reaches the limit for the number of stats.log files, each time Integration Server rotates the stats.log, Integration Server deletes the oldest archived stats.log file. If you set watt.server.stats.logFilesToKeep to 1, Integration Server keeps the current stats.log file and no previous stats.log files. That is, when Integration Server rotates the stats.log, Integration Server does not create an archive file for the previous stats.log. If you set watt.server.stats.logFilesToKeep to 0, or any value less than 1, Integration Server keeps an unlimited number of stats.log files. The default value of watt.server.stats.log.filesToKeep is 0.

If you reduce the number of stats.log files that Integration Server keeps and then restart Integration Server, the existing logs will not be pruned until Integration Server rotates the stats.log.

Integration Server uses the following naming format for the archived stats.log files: stats.yyymmdd_hhmmss.log where the timestamp indicates the time at which Integration Server archived the log file

Specifies the file size at which Integration Server rolls over the stats.log. Set this property to N[KB|MB|GB], where N is any valid integer. The minimum size at which Integration Server rotates a stats.log is 33KB. If you use KB as the unit of measure, you must set N to a value greater than or equal to 33. If you do not specify a unit of measure, Integration Server treats the supplied N value as bytes. In this case, N must be greater than or equal to 32768 to take effect. Do not include any spaces between the integer and the unit of measure. If an invalid value is specified, Integration Server proceeds as if no value was specified for the parameter. If you set the value using the Extended Settings page in Integration Server Administrator, validation prevents an invalid value from being saved.

There is no default value for this parameter. That is, by default, the parameter has no value. If no value is specified for watt.server.stats.logRotateSize, Integration Server rotates the stats.log at the interval specified by watt.server.statsLogRotateInterval only.

Specifies the number of seconds between updates of statistics loggings. For a stand-alone Integration Server, the watt.server.stats.pollTime must be an integer greater than or equal to 0 (zero). For an Integration Server in a cluster, the watt.server.stats.pollTime must be an integer greater than 0 (zero) but less than or equal to 60. The default is 60.

Integration Server Administrator displays this value as the interval of the Statistics Log task on the Server > Scheduler > View System Tasks page.

Specifies the length of the log recycle interval (in minutes) for the stats.log file. The recycle interval is the period of time that Integration Server retains statistics log records. The default is 1440 (24 hours).

Integration Server Administrator displays the watt.server.statsLogRotateInterval value as the interval for the Stats Log Recycle task on the Server > Scheduler > View System Tasks page. Integration Server Administrator displays this value in seconds instead of minutes. For example, if you set watt.server.statsLogRotateInterval to the default value of 1440, Integration Server Administrator displays the value for the Log Recycle interval as 86400 seconds. For more information about viewing system tasks, see Viewing Scheduled User Tasks.

After Integration Server startup, Integration Server immediately begins rotating the stats.log at the time specified by the watt.server.statsLogRotateInterval. If you set watt.server.statsLogRotateInterval to 2 minutes and Integration Server started at 9:30 pm, Integration Server rotates the stats.log at 9:32, 9:34, 9:36, and so forth. An exception to this behavior is that when the log recycle time is greater than the time from Integration Server startup to midnight, Integration Server first rotates the stats.log at midnight. Thereafter, Integration Server rotates the log at the specified interval. For example, if the watt.server.statsLogRotateInterval is set to 300 minutes (5 hours) and Integration Server starts up at 9:30 pm, Integration Server rotates the stats.log file at midnight and thereafter rotates the stats.log every 5 hours

Specifies whether the pub.storage:lock service adds the specified key to the data store if the key does not exist in the data store at the time the service executes. Set this parameter to true to have the pub.storage:lock service add the specified key to the data store if the key does not exist at the time the service executes. The pub.storage:lock service creates the specified key, assigns it a NULL value, and then locks the entry in the data store. Set this parameter to false if you do not want the pub.storage:lock service to add the key to the data store. The pub.storage:lock service is a NOP (no operation) if the specified key value does not exist in the data store. The default value is false. For more information about the pub.storage services, see the webMethods Integration Server Built-In Services Reference.

Specifies the maximum number of milliseconds a pub.storage service will hold a lock. The default value is 180000 milliseconds (3 minutes). For more information about the pub.storage services, see the webMethods Integration Server Built-In Services Reference.

Specifies the maximum number of milliseconds a pub.storage service will wait to obtain a lock. The default value is 240000 milliseconds (4 minutes). For more information about the pub.storage services, see the webMethods Integration Server Built-In Services Reference.

Specifies how often (in seconds) Integration Server deletes expired pub.storage locks. An expired pub.storage lock is one that is older than the value specified on the watt.server.storage.lock.maxDuration parameter. The default is 5 seconds. If the watt.server.storage.lock.sweepInterval parameter is set to a value less than one, Integration Server ignores the setting and uses 5 seconds instead. Integration Server does not have to be restarted for changes to this property to take effect. For more information about the pub.storage services, see the webMethods Integration Server Built-In Services Reference.

Specifies whether Integration Server will log HTTP 401 Access Denied as an error and trigger a notification. When this property is set to true, Integration Server will log HTTP 401 AccessDenied as an error and trigger notifications. When this property is set to false, Integration Server will not log HTTP 401 Access Denied as an error and will not trigger a notification. The default is false.

Specifies whether, when running a C service in Designer, Integration Server should write the warning messages issued about the missing variables to the server log. When this property is set to true, Integration Server does not write these messages to the server log. When this property is set to false, Integration Server writes messages about missing variables to the server log. The default is false.

Specifies the time period that a lock object exists for a given key for which a notification has been issued. After calling a pub.sync:notify service to create the notification, a pub.sync:wait can receive the notification. Any thread that is waiting for a notification for the key, receives the notification as long as the lifespan of the wait request overlaps with the lifespan of the notification. However, if a thread with an exclusive wait is registered for the notification key before any other service is waiting, the notification ends as soon as the exclusive wait receives the notification. The default is 60 seconds.

Specifies the length of time, in minutes, a thread can remain in the thread pool. When this length of time is reached and the thread has been used the maximum number of times as specified by the watt.server.thread.usage.limit parameter, Integration Server waits until the service is complete and releases the thread from the pool. A value of -1 indicates that threads can remain indefinitely in the thread pool. The default is 60 minutes.

Specifies the maximum number of times a pooled thread can be used. When this maximum number is reached and the length of time specified by the watt.server.thread.aging.limit parameter is reached, Integration Server waits until the service is complete and releases the thread from the pool. A value of -1 indicates that threads can be reused indefinitely. The default is 1000.

Controls whether the thread kill facility is enabled. This facility allows you to cancel or kill service threads in cases where a service is unresponsive. When you cancel a thread, Integration Server frees up resources that are held by the thread. When you kill a thread, Integration Server stops the thread, releases it from the thread pool, and replenishes the thread pool. The default is true. When the thread kill facility is enabled, you can cancel or kill threads by going to the Server > Statistics > System Threads screen. For more information about canceling and killing threads, refer to Canceling and Killing Threads Associated with a Service.

Specifies whether Integration Server should interrupt a service for which a timeout is triggered or is cancelled. If set to true, when a timeout is triggered or the service is cancelled, Integration Server interrupts the service thread that is executing a service. The default is false.

Controls how Integration Server handles the timeout setting of flow steps. Flow steps have a timeout property that controls how long the step can run. By default (true), when the step has exceeded the timeout period, Integration Server raises a FlowTimeoutException, and flow execution continues with the next step. When this property is set to false, it is possible for the flow step to run beyond its timeout period, in some cases. For instance, if a flow step calls another service, for example ServiceA, and ServiceA is executing when the timeout period has passed, ServiceA will continue executing past the timeout period. When ServiceA ends, it passes control back to the parent flow service, which then issues an exception.

Specifies the maximum number of threads that the server maintains in the thread pool that it uses to run services. If this maximum number is reached, the server waits until services complete and return threads to the pool before running more services. The default is 75.

Specifies the minimum number of threads that the server maintains in the thread pool that it uses to run services. When the server starts, the thread pool initially contains this minimum number of threads. The server adds threads to the pool as needed until it reaches the maximum allowed, which is specified by the watt.server.threadPool setting. The default is 10.

If an error occurs while Integration Server tries to resolve an uncompleted XA transaction, specifies the maximum length of time (in minutes) during which Integration Server should make additional attempts. The default is 5 minutes.

If an error occurs while Integration Server tries to resolve an uncompleted XA transaction, specifies the length of time (in seconds) that Integration Server waits between additional attempts. The default is 30 seconds.

Specifies the maximum number of unique XA transactions in an XA recovery log file. When the XA recovery log file reaches the maximum number of transactions, Integration Server creates a new file. The default is 2000 transactions.

Consider increasing the maximum number of unique XA transactions for the XA recovery log file if there are more than 2000 active XA transactions and Integration Server exhibits a performance delay due to input/output. Increasing the number of unique XA transactions allowed per file decreases the number of files used for the XA recovery log, which, in turn, may result in fewer files for Integration Server to search when performing XA recovery.

Decreasing the number of unique XA transactions stored in file may help during transaction recovery as it might decrease the time to read and consolidate open transactions.

Specifies whether Integration Server writes transaction information to the XA recovery store. Set to true to instruct Integration Server to log information about the state and progress of each XA transaction. Set to false to instruct Integration Server to skip logging XA transaction information. The default is true.

Specifies whether or not a request to shut down the Integration Server interrupts the retry process for a webMethods messaging trigger service. If this parameter is set to false, Integration Server waits for the maximum retry attempts to be made before shutting down. Integration Server will also shut down if the trigger service executes successfully during a retry attempt. If this parameter is set to true, Integration Server waits for the current service retry to complete. If the webMethods messaging trigger service needs to be retried again (the service ends because of an ISRuntimeException), the Integration Server stops the retry process and shuts down. Upon restart, the transport (Broker, Universal Messaging, or, for a local publish, the transient store) redelivers the document to the trigger for processing. The default is false.

Specifies whether Integration Server should bypass decoding that is normally performed when documents are retrieved from the Broker on behalf of a webMethods messaging trigger. If this property is set to true, Integration Server passes the value of the Broker event to the trigger service in an object called $brokerEvent and no decoding is performed. Set this parameter to true if Integration Server is receiving native Broker events. The default is false.

For more information about publishing native Broker events, see the Publish-Subscribe Developer’s Guide.

Specifies whether Integration Server should strictly enforce a locally published document's time-to-live. When this parameter is set to true, before processing a locally published document in a trigger queue, Integration Server determines whether the document has expired. Integration Server discards the document if it has expired. The default is false.

Specifies a comma-delimited list of triggers to exclude from the webMethods Messaging Trigger Management pages in Integration Server Administrator. Integration Server also excludes these webMethods messaging triggers from trigger management changes that suspend or resume document retrieval or document processing for all triggers. Integration Server does not exclude these webMethods messaging triggers from changes to capacity, refill level, or maximum execution threads that are made using the global trigger controls (Queue Capacity Throttle and Trigger Execution Threads Throttle).

You can specify the fully qualified names of all the webMethods messaging triggers that you want to exclude. You can also use pattern matching to exclude a group of triggers by specifying the beginning portion of the fully qualified name and following it with an asterisk (*). The Integration Server excludes all triggers that begin with the supplied pattern. For example, if you want to exclude all triggers located in the pub.prt folder, specify:

Specifies the interval, measured in seconds, at which Integration Server executes resource monitoring services for webMethods messaging triggers. A resource monitoring service is a service that you create to check the availability of resources used by a trigger service. When it suspends a webMethods messaging trigger because all retry attempts have failed, Integration Server executes the resource monitoring service to determine if all the resources are available. The default is 60 seconds.

For more information about resource monitoring services, see the Publish-Subscribe Developer’s Guide.

Indicates whether Integration Server schedules a system task to monitor the document history database when a ConnectionException causes a transient error occurs during trigger preprocessing. A ConnectionException indicates that the document history database is not enabled for exactly-once processing or is not properly configured.

When this property is set to true, Integration Server schedules a system task that executes an internal service that monitors the connection to the document history database. When the document history database is enabled for exactly-once processing or is properly configured, the internal service indicates that the connection to the document history database is available. Then, Integration Server resumes the trigger and re-executes it when the connection to the document history database is available.

When this property is set to false, Integration Server does not schedule a system task to check for the database's availability and will not resume the trigger automatically. You must manually resume the trigger after configuring the document history database properly.

The default is false

Indicates whether Integration Server suspends a trigger if an error occurs during the preprocessing phase of trigger execution. The preprocessing phase encompasses the time from when the trigger retrieves the document from its local queue to the time the trigger service executes. When this property is set to true, the trigger property On Retry Failure is set to Suspend and retry later, or the trigger property On Transaction Rollback is set to Suspend and recover, Integration Server suspends a trigger if one of the following occurs during preprocessing:

When this property is set to false and the trigger property On Retry Failure is set to Throw Exception or the trigger property On Transaction Rollback is set to Recover only, Integration Server does not suspend the trigger if a trigger preprocessing error occurs. If the document history database is not available, Integration Server

The default value for watt.server.trigger.preprocess.suspendAndRetryOnError is false.

For more information about building a resource monitoring service, see the Publish-Subscribe Developer’s Guide or Using webMethods Integration Server to Build a Client for JMS. For more information about transient error handling during trigger preprocessing, see webMethods Service Development Help.

Specifies whether Integration Server deletes document type subscriptions for webMethods messaging triggers when the package containing the trigger reloads or an update of the package is installed. If this property is set to true (the default) and a package reloads or an update of the package is installed, Integration Server deletes and then recreates any document type subscriptions for webMethods messaging triggers in the package. (If Integration Server connects to a Broker, Integration Server deletes and recreates the subscriptions on the trigger client on the Broker.) This creates a small window of time during which the document type subscriptions do not exist. During this window, the trigger will not receive documents to which it normally subscribes.

If this property is set to false, Integration Server does not delete and then recreate document type subscriptions for webMethods messaging triggers when the package reloads or is updated. Although Integration Server creates new document type subscriptions for triggers, Integration Server does not modify existing subscriptions. Specifically, if a trigger deleted a document type subscription, the subscription will not be removed when the package reloads or is updated. Consequently, when this property is set to false, the trigger might receive document types to which it no longer subscribes because the deleted document type subscriptions still exist on the trigger client on the Broker. When working with a 6.5.2 version of webMethods Broker, you can use My webMethods to delete the obsolete document type subscriptions from the trigger client on the Broker. The default is true.

Indicates whether instances of a webMethods messaging trigger use the same session on Integration Server when the document locale is the same as the default locale of Integration Server. When this property is set to true, Integration Server checks the locale of the document before processing it. If the document locale is the same as the default locale of Integration Server, or no locale is specified, the trigger uses a shared session. If the document locale is different from the default, then Integration Server creates a new session for the trigger to use to process that document. When this property is set to false, Integration Server uses a new session for each instance of a trigger. The default is false.

Reusing sessions for a webMethods messaging trigger might improve performance. However, this property does not work with all adapters.

Specifies when Integration Server should suspend a webMethods messaging trigger. A trigger can be suspended when both the following occur:

When Integration Server suspends a webMethods messaging trigger, it halts document processing and document retrieval for the trigger. Suspending the trigger prevents Integration Server from acknowledging the document and prevents the messaging provider from discarding the document. After suspending the trigger, Integration Server monitors the connection to the audit database and resumes the trigger (document processing and document retrieval) when the connection to the audit database is re-established. Integration Server retrieves the unacknowledged document from the messaging provider and attempts to process it again.

Set the watt.server.trigger.suspendOnAuditErrorWhen parameter to one of the following values:

The watt.server.trigger.suspendOnAuditErrorWhen configuration parameter only applies when the audit subsystem is configured to write data synchronously.

Specifies the absolute directory path of the hard disk drive space in which the Integration Server is to temporarily store large documents rather than keep them in memory. Each file that the Integration Server stores in this directory is given the name DocResxxxxx.dat, where xxxxx is a value that can vary in length and character. Specify the absolute directory path to a directory on the same machine as the Integration Server. The default value is JVM's temporary directory (i.e., the value of java.io.tmpdir).

Example: If you want the Integration Server to use the LargeDocTemp directory on your D drive, specify the following:

If you have a cluster of Integration Servers, each one must have its own Tspace.

Specifies the maximum number of bytes that can be stored at any one time in the hard disk drive space that you defined using the watt.server.tspace.location property. If the Integration Server attempts to write a large document to the hard disk drive space that will cause the number of bytes you specify to be exceeded, an error message is displayed on the server console, and the document is not stored. Specify a positive whole number of bytes. The default value is 52,428,800 bytes (50 MB).

Example: To set the maximum number of bytes that can be stored to 30,000,000 bytes, specify the following:

Specifies the amount of time in milliseconds that documents can remain in the Tspace before they are deleted. If a document remains in the Tspace longer than the value defined by this parameter, the document expires and becomes eligible for removal from the Tspace. Expired Tspace documents are removed when the Tspace begins to run low on free disk space. The default is 0.

Specifies the email address of an administrator to notify when guaranteed delivery capabilities are disabled due to an error (for example, if the Integration Server encounters a disk full condition or if the audit-trail log is full). There is no default.

Specifies the number of seconds a cluster server waits before breaking a lock on a job in a cluster job store. The default is 120.

You must be using webMethods Integration Server Clustering to use this setting. For more information, refer to the webMethods Integration Server Clustering Guide.

Specifies the number of milliseconds a cluster server sleeps between attempts to place an update lock on a job in a cluster job store. The default is 100.

You must be using webMethods Integration Server Clustering to use this setting. For more information, refer to the webMethods Integration Server Clustering Guide.

Specifies whether the Integration Server is to re-execute services for guaranteed delivery transactions in the job store that are pending when the Integration Server is restarted after a failure. If a transaction is pending, the service began execution before the Integration Server failed.

If the setting is true, the Integration Server resets the transaction status from pending to new, and the service will be re-executed. If the setting is false, the Integration Server resets the transaction status from pending to fail to indicate the heuristic failure, and the service will not be re-executed. The default is true.

Specifies the number of seconds between sweeps (clean up) of the job store for inbound guaranteed delivery transactions. The server sweeps the job store to remove expired transactions. The default is 60.

Specifies the number of attempts made by Integration Server in publishing a guaranteed document to a Universal Messaging server, after the initial attempt at publishing fails because of a transaction failure. The maximum number of retries is nine. If you try to assign a value greater than nine, Integration Server automatically sets the value of the property to nine. The default is zero.

When setting a retry value, you must ensure that the value of the total transaction timeout does not exceed the value of the MaxTransactionTime property. The total transaction timeout value is calculated by multiplying the total number of retry attempts with the value of the EventTimeout property. For example, if the retry value is set to 9, and the EventTimeout is set to 60s, the total transaction timeout is 60(9+1)= 600s.

Specifies whether Integration Server enables partial matching on URL aliases. If you set this server configuration parameter to true and define a URL alias in Integration Server Administrator, Integration Server enables partial matching on URL aliases. The default is false.

When partial matching is enabled Integration Server considers an alias a match if the entire alias matches all or part of the request URL, starting with the first character of the request URL path.

For information about partial matching and defining URL aliases, see Setting Up HTTP URL Aliases. For specific information about partial matching for REST resources configured using the legacy approach, see REST Developer’s Guide.

Specifies the FTP root directory that the Integration Server will create at startup. When any Integration Server user logs into the FTP Listener, the server creates that user's FTP home directory in this root directory, for example FtpRoot/username. You can specify any directory to be the root directory, including a mapped network directory. If this property is not defined, a default directory named userFtpRoot is created in your Integration Server home directory.

The user who connects to Integration Server through FTP listener is placed either in the default FTP root directory or the client user directory as defined in the watt.server.login.userFtpDir property.

Administrators, Replicators, and non-privileged users can perform put and get operations in the following directories:

When a user completes a put command in his or her own user directory (that is, when the STOR command is completed on the server side but before the server acknowledges the client with return code 226), an event is fired to notify interested parties by publishing a pub.client.ftp:putCompletedNotification document to the webMethods Broker. EDI packages will subscribe to this document and will retrieve the file just put onto the server.

Specifies whether Integration Server uses the 7.1x handler chain processing behavior when executing handlers for a web service descriptor created in 7.1x. When set to true, Integration Server uses the handler chain processing behavior available in Integration Server version 7.1x for a 7.1x web service descriptor. When set to false, Integration Server uses the handler chain processing behavior available in Integration Server 8.0 for a 7.1x web service descriptor. The default is false.

This is an internal property. Do not modify.

Specifies the prefix assigned to the namespace http://www.webMethods.com/2001/10/soap/encoding for use in details for SOAP faults. The default is webM.

For a provider web service descriptor for which thePre-8.2 compatibility mode property is set to true, specifies whether the target namespace of the top-level element in the response uses the target namespace of the top-level element in the request. When set to true, a web service response sent by the Integration Server uses the target namespace of the top-level element in the request as the top-level namespace of the response. While this is incorrect behavior, it provides backward compatibility. If existing web service clients failed because the client expected a response that used the namespace of the top-level element of the request and you want to allow existing clients to continue to process responses without any changes to the client, set watt.server.ws.responseTNS.from.request to true.

When set to false, Integration Server uses the target namespace of the provider web service descriptor as the namespace of the top-level element in the response. This is the correct behavior. The default value is false.

Specifies the maximum number of seconds that the web services client and host clocks can differ so that the timestamp expiry validation does not fail. Integration Server validates the inbound SOAP message only if the creation timestamp of the message is less than the sum of the timestamp maximum skew value and the current system clock time.

You can use this parameter to set the timestamp maximum skew value when Integration Server uses WS-Security policy to implement security and if you have not set a value in the Timestamp Maximum Skew field in the Create web Service Endpoints Alias screen. The value must be a positive integer or zero. The default is 300 seconds.

Specifies whether the timestamp placed in the Timestamp element of the security header of an outbound message is precise to seconds or milliseconds. If you set the precision to milliseconds, Integration Server uses the timestamp format yyyy-MM-dd'T'HH:mm:ss:SSS'Z'. If you set the precision to seconds, Integration Server uses the timestamp format yyyy-MM-dd'T'HH:mm:ss'Z'.

You can use this parameter to set the precision when Integration Server uses WS-Policy to implement WS-Security and if you have not set a value in the Timestamp Precision field in the Create Web Service Endpoints Alias screen. Set this property to true, if you want the timestamp precision set to milliseconds. Set this property to false, if you want the timestamp precision set to seconds. The default is true.

Specifies the time-to-live value for an outbound message in seconds. Integration Server uses this value to set the expiry time in the Timestamp element of outbound messages.

You can use this parameter to set the time-to-live value when Integration Server uses WS-Policy to implement WS-Security and if you have not set a value in the Timestamp Time to Live field in the Create web Service Endpoints Alias screen. The value must be an integer greater than 0. The default is 300 seconds.

Specifies whether Integration Server prints debug information to standard out and stack traces to standard error while generating or consuming WSDL. When set to true, Integration Server prints debug information to standard out and stack traces to standard error. The default is false.

Specifies the encoding that Integration Server must use when processing incoming XML files.

If an encoding is not defined in the XML header, Integration Server attempts to process the XML file using the charset encoding of the http or ftp request. If charset encoding is not available in the request header, then Integration Server uses the character encoding specified in the watt.server.xml.encoding server configuration parameter. There is no default value for this parameter.

Specifies whether the server will throw an exception when the XML parser detects a malformed entity. If the value is set to true, the server will throw an exception when it detects a malformed entity in an XML or DTD. If the value is set to false (the default), the server will allow malformed entities and does not throw an exception.

Specifies whether the pub.xml:xmlNodeToDocument service keeps additional occurrences of an element in an XML node when arrays are not created (the makeArrays input parameter is set to false). This parameter also determines whether or not the pub.event.eda:eventToDocument service keeps additional occurrences of an element in the XML document passed into the service. When set to true, the document produced by the pub.xml:xmlNodeToDocument service contains multiple occurrences of the element. When set to false, the document produced by the pub.xml:xmlNodeToDocument service keeps only the last occurrence of the element. The default is true.

For example, suppose the following XML node is provided as input to the pub.xml:xmlNodeToDocument service:

When watt.server.xml.xmlNodeToDocument.keepDuplicates is set to true, the pub.xml:xmlNodeToDocumentservice produces this document:

When watt.server.xml.xmlNodeToDocument.keepDuplicates is set to false, the pub.xml:xmlNodeToDocument service produces this document:

Note that only the last <e1> element in the source XML is retained in the resulting document.

Specifies how Integration Server decodes duplicate elements contained in an anyType element. Set watt.server.xml.xmlNodeToDocument.makeArrayforWS to true if you want Integration Server to create an array for duplicate elements contained in an element of type anyType. Set this parameter to false if you want Integration Server to leave duplicate elements as separate, repeated elements in the element defined to be of type anyType. When set to false, Integration Server does not create an array for elements that appear more than once in the element defined to be of type anyType. The default is false.