Enables or disables verbose logging for BrokerTypeCoder. If set to true, Integration Server enables verbose logging for BrokerTypeCoder. The default is false.

Specifies the wire type Integration Server uses to encode and decode Broker messages. The default is 3.

The following table lists the possible settings:

Indicates whether Integration Server should initialize the pool with minimum pattern matcher pool objects specified. If set to false (the default) Integration Server initializes the pool whenever it parses or validates a schema. If the delayFill is set to true, Integration Server does not initialize the pool.

Specifies the maximum number of pattern matcher pool objects Integration Server allows in a pool. The default is 50.

Specifies whether Integration Server uses the Java regular expression compiler during validation. When watt.core.datatype.usejavaregex is set to true, during XML validation, Integration Server uses the Java regular expression compiler and Integration Server performs pattern matching as described by java.util.regex.pattern. When set to false, during XML validation, Integration Server uses the Perl regular expression compiler and uses pattern matching. The default is false.

Specifies the namespace element Integration Server uses to create a service URI. Specify a String value that indicates the hostname. The default is localhost.

Specifies the prefix Integration Server uses for a type name. This is appended to the type name to form a local name. The default is __ (two underscores).

When generating the schema definition in a WSDL, indicates whether Integration Server omits the xsd:any element in the complex type definition that corresponds to an open document. A document variable is considered open when the Allow unspecified fields property is set to true. When watt.core.schema.createSchema.omitXSDAny is set to true, the xsd:any element is omitted from the schema portion of the WSDL document even if the document variable has the Allow unspecified fields property is set to true. When watt.core.schema.createSchema.omitXSDAny is set to false, Integration Server includes the xsd:any element in the complex type definition only if the corresponding document variable has the Allow unspecified fields property is set to true. The default for watt.core.schema.createSchema.omitXSDAny is true.

When generating an IS document type from an XML schema definition, indicates whether or not Integration Server generates IS document types for all complex types regardless of whether the types are referenced or not. When this property is set to true, Integration Server generates an IS document type for every complex type definition in the XML schema. When this property is set to false, Integration Server generates a separate IS document type for a complex type only if the complex type is referenced or is derived from a referenced complex type. The default is false.

Used to create a service URI, in the format - 'http://' authority path '/' service-name, authority stands for the value specified by this property. String value usually indicating the hostname.

When generating an IS document type from an XML schema definition that contains a substitution group, indicates whether the resulting document type contains an optional element for each member of a substitution group. When this property is set to false, the resulting document type contains a field that corresponds to the head element in the substitution group, but does not contain any elements for members of the substitution group. When this property is set to true, the resulting document type contains a field that corresponds to the head element and fields that correspond to each member element of the substitution group. All the fields, including the head element, are marked as optional elements. The default is false.

Specifies the number at which a maxOccurs value greater than this number is treated as unbounded. When validating a document against an IS schema with an element for which maxOccurs is greater than the watt.core.schema.useUnboundedForMaxOccurs, Integration Server validates the instance document as if the value of the maxOccurs were unbounded. Treating maxOccurs as unbounded may prevent an OutOfMemoryError from occurring during validation when the maxOccurs value is large, such as 9999. There is no default value for this parameter, indicating that Integration Server uses the value specified in the schema as the maxOccurs value.

This is an internal property. Do not modify.

Indicates whether Integration Server HTML encodes the output from a flow service and %value Variable% tag in a DSP or output template. When this property is set to true, the value of %value Variable% tags, including XML and JavaScript, is HTML encoded. Having Integration Server HTML encode the values helps prevent cross-site scripting attacks. When this property is true, you can still indicate that you do not want Integration Server to HTML encode the output of a %value Variable% tag by including the encode(none) option (%value Variable encode(none)%). When this property is set to , the values of %value Variable% tags are not encoded, and, as a result, DSP pages or pages resulting from output templates might be vulnerable to cross-site scripting attacks. In case of a flow service, when this property is set to true, the output (characters such as, "<", ">", and so on) from a flow service is encoded. Setting the property to false disables the encoding of a flow service output. The default is true.

For DSP pages, this parameter controls whether Integration Server performs secure UfalseRL redirection. Internal DSP pages commonly use the variable names “url” and “returnurl” with the %value% tag to indicate to Integration Server that URL redirection can occur in the client. As a result, whether a DSP page is an internal DSP page or a custom DSP page, when Integration Server encounters the variable name “url” or “returnurl” for a %value% tag, it assumes that the value is meant for URL redirection.

When the watt.core.template.enableSecureUrlRedirection parameter is set to true, Integration Server uses secure URL redirection. When performing secure URL redirection, if the %value% tag uses the variable name “url” or “returnurl”, Integration Server checks the URL to determine whether it is a relative path to a location within Integration Server (e.g., ..\redirectedurl.dsp) or another value. If it is a relative path, Integration Server considers a redirection to the URL to be safe, and as a result, takes no action. However, for other values, Integration Server assumes the URL to be an external URL (e.g., http://example.com) and alters the output, even if the intent of the %value% tag is not to redirect to the URL. Integration Server alters the URL so that if an attempt is made to redirect to the external URL, the redirection goes to an error page. Integration Server alters the URL by prepending the value “error.dsp?data=” to the output of the %value% tag (e.g., error.dsp?data=http://example.com).

Setting this parameter to false disables secure URL redirection and, as a result, might put your applications at risk.

You should use the variable “url” or “returnurl” with the %value% tag only when you want to redirect to an internal URL. If you have existing applications that use the variable name “url” or “returnurl”, Software AG recommends that you update your applications and do not use these variable names except for internal URL redirection. If you do not want to change the variable names in existing applications, you can set watt.core.template.enableSecureUrlRedirection parameter to false.

The default setting for the watt.core.template.enableSecureUrlRedirection parameter is true.

Specifies whether to skip a validation that Integration Server performs when decoding mixed content elements that have an enumeration restriction. The validation returned an error when optional missed content was absent, because an empty value was not listed as an option in the enumeration set for the *body field. When set to true, Integration Server skips this validation and treats the *body as completely optional, allowing empty or absent *body values to pass validation.

When set to false, Integration Server performs the validation. The default value is false.

Changes to this property take effect immediately.

Specifies whether the pub.schema:validate service is to validate multiple roots when processing multi-part documents. When this property is set to true, the pub.schema:validate service checks for multiple root nodes. If multiple root nodes are found, the service flags a validation error. When this property is set to false, the pub.schema:validate service does not perform multiple root validations. The default is true.

Specifies whether Integration Server generates errors during document validation if mandatory fields are missing from the document. When watt.core.validation.skipMandatoryFields is set to true, Integration Server does not generate validation errors during document validation even if required fields are missing from the document. When this parameter is set to false, Integration Server generates validation errors if required fields are missing from the document. The default is false. This parameter affects document validation performed by the pub.schema:validate service and SOAP request and SOAP response validation.

Indicates whether or not Integration Server skips validation of references to elements that are not namespace qualified made from within a namespace qualified element during XML validation against a schema. Set to true if you want Integration Server to skip validation of these referenced elements. Set to false if you want Integration Server to validate these referenced elements. The default is false.

Indicates whether Integration Server evaluates instances of data types for illegal values during XML validation according to the W3C recommendation XML Schema Part 2: Datatypes. If you want Integration Server to validate data types consistent with the W3C recommendation, set watt.core.validation.w3cConformant to true. The default is false.

Identifies a list of trusted external entities (file URIs, HTTP URLs, and so on) that contain XML content to transform in an XML or XSLT file. Use a comma to separate each entity.

The pub.xslt.Transformations:transformSerialXML service loads the content for any entity in this list that is referenced either in the XML that the service receives or in the XSLT stylesheet the service uses to transform the XML. The service reads this list in the following situations:

Indicates whether the pub.xml:loadXMLNode and pub.xml:xmlStringToXMLNode services should return expanded general (internal and external) entities. Also indicates whether the pub.xslt.Transformations:transformSerialXML service should allow external entities. When this parameter is set to true, the loadXMLNode and xmlStringToXMLNode services expand references to general entities, and the transformSerialXML service allows external entities. When this parameter is set to false, the loadXMLNode and xmlStringToXMLNode services ignore references to general entities, and the transformSerialXML service blocks external entities. The default is true.

Indicates whether, while creating the XSD, Integration Server should use the node’s path for the URI and the namespace name for the node and schema. If set to true, Integration Server generates the URI based on the node's path. This URI is then used as the namespace name for the particular node or schema. If set to false (the default), Integration Server sets the namespace to null.

Specifies whether Integration Server should use the URI generated for the message as the namespace name for the WSDL message. If set to true (the default), Integration Server uses the URI generated for the message as the namespace name for the WSDL message only if the style is non-RPC. If set to false, Integration Server sets the namespace to null.