When creating a document type from XML string in Integration Server, an XML external entity attack was possible during the validation of XML string.

The issue is now resolved. After the fix, Integration Server rejects such XML with the following message - "XML provided is not well-formed or external references encountered while parsing XML - <specific error message>". - "

Application Platform does not initialize properly when Integration Server startup does not complete within 5 minutes.

To resolve this issue, Integration Server registers the OSGi services before continuing with the rest of startup. This allows Application Platform to initialize properly even if Integration Server takes longer than 5 minutes to complete startup.

Element in outbound SOAP message is associated with the incorrect namespaces.

When an attribute on an element redefines the XML namespace prefix for an element to be a different URL from the one defined in the WSDL document and WS-Security processing is engaged, the element in the outbound SOAP message is associated with the incorrect namespace.

This issue is now resolved.

Generation of a consumer web service descriptor or WSDL first provider web service descriptor fails with a WSDLException.

If a WSDL document contains an empty targetNamespace attribute, an attempt to create a web service descriptor from the WSDL document fails with the following exception:

WSDLException: faultCode=PARSER_ERROR: Problem parsing '- WSDL Document -'.: org.xml.sax.SAXParseException: The value of the attribute "prefix="xmlns",localpart="tns",rawname="xmlns:tns"" is invalid. Prefixed namespace bindings may not be empty.

Now, when creating a web service descriptor from a WSDL document that contains an empty targetNamespace attribute, Integration Server no longer generates the xmlns:tns= attribute.

Note: This fix resolves the issue for consumer web service descriptors completely. However, to fully resolve the issue for WSDL first provider web service descriptors, you must also install a Web Services Stack fix that includes WSSTACK-2783.

The enhanced XML parser throws an ArrayIndexOutOfBoundsException when more than 20 attributes are present on a node.

With this fix, there is longer a limit to the number of attributes on a node which prevents the ArrayIndexOutOfBoundxException.

Integration Server does not close a socket connection after SSL handshake fails.

If Integration Server establishes the socket connection using JSSE and then if the SSL handshake fails, the socket connection remains open.

The issue is now resolved. Integration Server now closes the socket connection after SSL handshake fails.

When entering quiesce mode Integration Server shuts down all cache managers available in a JVM instead of just the cache managers started by Integration Server.

This issue is now resolved.

When editing existing keystore and truststore aliases, the configured “Type” and “Provider Type” fields show incorrect input.When editing existing keystore and truststore aliases properties, the valuesor the “Type” and “Provider” fields are reset to “JKS” and “SUN” instead of the configured values set during the creation of keystore and truststore aliases.

The issue is resolved. Integration Server now preserves the settings used during the creation of keystore and truststore aliases.

Long latencies observed when using SFTP.

Concurrent execution of the pub.client.sftp:login service and/or methods in the underlying class com.wm.app.b2b.server.sftp.client.SFTPSessionManager may result in long latencies which are caused by synchronization.To address this issue and improve multi-threading support, synchronization statements deemed unnecessary were removed.

Enhancements in web service connectors to process messages in an order.

When creating a consumer web service descriptor from a WSDL document, Integration Server creates a web service connector for each operation contained in the WSDL document. These connectors do not provide a facility to process messages in an order.

The issue is now resolved. Integration Server now uses message numbers that are unique identifiers used by the reliable messaging sequence.

FTP thread hangs during FTP put operation.

During an FTP file transfer using the FTP put command from client to server, where Integration Server acts as the server, if a network issue occurs, then the FTP thread hangs and it never times out. This issue happens only in Passive mode.

The issue is now resolved.

Integration Server acting as FTPS client cannot connect to an FTPS server.

An Integration Server acting as FTPS client cannot connect to an FTPS server using JSSE. Integration Server uses JSSE when the secure/useJSSE input parameter for the pub.client.ftp* service is set to yes.

The issue is now resolved.

When watt.net.http401.throwException is false and the pub.client:http service does not get a response from the server to which it is trying to connect, Integration Server throws a NullPointerException instead of a ServiceException.This issue is now resolved.

Integration Server throws a ConcurrentModificationException when initializing a connection from a JDBC connection pool.

This issue is resolved by updating methods in an internal class to use locking.

Public service setKeyAndChainFromBytes does not work properly if the SSL key differs from the default SSL key in Integration Server Administrator.

If an SSL key is configured in the Integration Server Administrator (Security > Certificates) is different from the one set using the setKeyAndChainFromBytes service, then Integration Server does not send the SSL key set by setKeyAndChainFromBytes service for connections using JSSE. Normally, SSL key set using the setKeyAndChainFromBytes service takes precedence over the one set in the Integration Server Administrator.

This issue is resolved now.

When using the Integration Server OData implementation to query the OData entity with a filter containing the ampersand character (&). For example: $filter=SAMPLE eq 'Text1 & Text2'), Integration Server returns an incorrect result.

Integration Server now returns a proper result; however, the query string that uses & must be properly encoded before Integration Server receives the query. For example: $filter=SAMPLE%20eq%20%27Text1%20%26%20Text2%27

The pub.document:searchDocuments service behaves differently than expected.

The pub.document:searchDocuments service functions differently from the expected behavior, which is documented in the webMethods Integration Server Built-In Services Reference.

This issue is now resolved.

No option to set custom truststore while invoking pub.client:http service.

The pub.client:http service uses the default truststore alias (DEFAULT_IS_TRUSTSTORE) while establishing a secure connection with HTTP server. Integration Server does not provide the option to set custom truststore while invoking this service.

This issue is resolved. Now, a new input parameter "trustStore" is included in pub.client:http service to set the custom truststore alias while invoking this service.

Integration Server does not validate the SSL certificate expiry while using JSSE.

Integration Server does not validate the SSL certificate expiry in a certificate chain of an incoming connection request from an Internet resource while it is configured to use JSSE. Hence, even if the certificate has expired, Integration Server does not reject the request.

This issue is now resolved.

Input parameter value of scheduled task is overwritten with the latest value of input parameter in flow service.

An assigned input value in scheduler task is overwritten with the latest value set for the corresponding flow service. This impacts the value of the input parameter in the scheduled task.

This issue is now resolved.

Execution of a web service connector ends with a NullPointerException.

Execution of a web service connector for a consumer web service descriptor generated from a WSDL document containing multiple service definitions ends with a NullPointerException. This occurs because Integration Server did not create the BRANCH steps correctly when creating the connector.

Now, Integration Server generates the correct BRANCH steps for web service connectors created from a WSDL document with multiple service definitions.

Note: After applying this fix, you must recreate or refresh the consumer web service descriptor to generate web service connectors with the correct BRANCH steps.

webMethods messaging trigger ends with the exception com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero).

If a publishable document type specifies an encoding type of Protocol buffers and saving changes to the document type results in warning messages about field names not being valid for protocol buffer encoding, trigger processing fails for instances of the publishable document type with the following exception:

com.wm.app.b2b.server.dispatcher.exceptions.MessagingCoderException: java.io.IOException:

com.google.protobuf.InvalidProtocolBufferException: Protocol message contained an invalid tag (zero)

This issue occurs because of an error in how Integration Server encodes the UnknownFieldSet when publishing a document. The UnknownFieldSet contains fields that cannot be represented in a protocol buffer message descriptor.

This issue is resolved by changing the way in which Integration Server encodes the UnknownFieldSet at the time of publication. This encoding change affects only those documents published after the fix is installed. Existing, unprocessed documents that use the improperly encoded UnknownFieldSet must be removed to prevent the occurrence of InvalidProtocolBufferException: Protocol message contained an invalid tag (zero). Make sure the client side queue for the Universal Messaging connection alias that publishes instances of the document type is empty. Additionally, make sure to use Universal Messaging Enterprise Manager to delete the channel associated with the publishable document type. Deleting the channel removes any instance documents encoded with the invalid zero key. Integration Server recreates the channel when it is restarted after fix installation.

Integration Server does not start if the distributed service results cache contains invalid entries.

If the distributed service results cache contains invalid entries, Integration Server exits with an error similar to the following.

Error occurred while initializing server:

java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1967) at com.wm.app.b2b.server.ostore.ServiceCacheImpl.getKeySvc(ServiceCacheImpl.java:350) at com.wm.app.b2b.server.ostore.ServerCache.load(ServerCache.java:110) com.wm.app.b2b.server.CacheManager.startSweeper(CacheManager.java:128) at com.wm.app.b2b.server.Server.run(Server.java:644)

This issue is now resolved.

Unable to restart Integration Server in a clustered environment.After installing a fix that contains PIE-45163, restarting Integration Server in a clustered environment fails if there is scheduled task with target set to 'All'. Also, the pub.scheduler:getTaskInfo service returns incorrect status of a running task.

These issues are now resolved.

Integration Server fails to read the restore file.

Integration Server throws an exception while restoring pipeline from file using the pub.flow:restorePipelineFromFile service. The issue has occurred because an incorrect data type was defined to one of the input fields in the file while saving pipeline.

This issue is now resolved.

Integration Server fails to update the REST API descriptor(RAD) containing REST V2 resources.

In Designer, while making changes to the REST V2 resources or the services associated with the operations of the resources, Integration Server fails to update the RAD that contains the REST V2 resources.

The issue is now resolved.

Decoding a dynamic parameter with unicode characters fails to decode accurately.

Integration Server fails to correctly decode the unicode characters in the dynamic parameter of a REST request.

This issue is now resolved.

Integration Server fails to add comments to the generated document.

When creating a REST API descriptor from a Swagger document, if a definition in the Swagger document contains comments, Integration Server fails to add those comments to the corresponding Comments tab of generated docTypes.

This issue is now resolved.

In a REST API descriptor, variables of type File get converted to type String.

When creating a REST API descriptor from a Swagger document, Integration Server represents a file type as a String instead of a document.

This issue is resolved. Since Integration Server does not support the File type, variables of type File are converted to Object type.

Integration Server clears the response code from a REST API descriptor.

When adding a new response code to a resource in REST API descriptor and then moving the resource from one package to another, Integration Server removes all the new response codes from REST API descriptor.

This issue is now resolved.

Unable to create a REST API Descriptor for REST resources with documents with cyclic references.

Creating a REST API descriptor for REST resources with services that have documents with cyclic references fail.

This issue is now resolved.

Clicking the Log Off link in Integration Server Administrator causes Internet Explorer to log the user out of all Integration Servers in all Internet Explorer tabs.

This issue is resolved. Clicking the Log Off link in an Internet Explorer tab now logs the user out of the Integration Server in the current tab only. If the user is logged in to the same Integration Server through multiple tabs, logging off the Integration Server on one tab logs the user off of that same Integration Server on the other tabs as well.

Integration Server displays '405 method not found' error while executing a URL at run time that is added to a REST API descriptor(RAD).

While adding two similar URLs to a RAD with different HTTP methods, Integration Server might display '405 method not found' error while executing one of theURLs during run time.

The issue is now resolved.

The pub.client:http service ends with a NullPointerException if useJSSE is set to yes and the default truststore is not configured.

If the default truststore is not configured, the watt.security.cert.wmChainVerifier.trustByDefault parameter is set to false, the pub.client:http service sets useJSSE to yes, the pub.client:https service ends with a NullPointerException but should not.

This issue is now resolved.

When migrating JDBC connection pools, Integration Server migration utility reports the following error. "Error message: String index out of range: -1"This issue occurs because of the non-XML files present in the <IntegrationServer_installDirectory>\instances\<instance_name>\config\jdbc\pool folder.

This issue is now resolved. Integration Server migration utility correctly migrates JDBC connection pools.

Integration Server displays incorrect error messages when certain services belonging to pub.string folder are invoked without the required inputs.

Integration Server throws incorrect error messages when the pub.string:tokenize , pub.string:numericFormat ,pub.string:padLeft , pub.string:padRight services are invoked.

com.wm.app.b2b.server.ServiceException: java.lang.NullPointerException is thrown and com.wm.app.b2b.server.ServiceException: java.lang.NumberFormatException

is thrown when invoked with invalid inputs.

This issue is now resolved. Now, Integration Server displays the following appropriate error messages:

com.wm.app.b2b.server.ServiceException: [ISS.0086.9249] Missing Parameter for incomplete inputscom.wm.app.b2b.server.ServiceException: [ISS.0086.9250] Parameter is not of type for invalid inputs

Package deployment fails with a NullPointerException when the Compile Java Services option is set to Yes.

Deploying a package that contains a Java service fails with a NullPointerException similar to the following when the Compile Java Services option is set to Yes:

java.lang.NullPointerException: nullat com.wm.lang.ns.NSService.setValues(NSService.java:717)at com.wm.lang.ns.NSNode.<init>(NSNode.java:93)at com.wm.lang.ns.NSService.<init>(NSService.java:149)at com.wm.app.b2b.server.BaseService.<init>(BaseService.java:201)

This issue is now resolved.

Enterprise Gateway blocks the IP address of the proxy used.

When a proxy is used between a client and Enterprise Gateway, then Enterprise Gateway blocks the IP address of the proxy. This is because, Enterprise Gateway ignores the X-Forwarded-For header in the request and hence during a Denial of Service attack check, instead of using the client IP address it uses the IP address of the proxy server.

This issue is resolved. Now, Integration Server checks for X-Forwarded-For header in request and if it is present, then Enterprise Gateway uses the client IP address from this header.

Invoking pub.string:numericFormat service with a decimal value for the 'num' parameter fails with error.

Invoking the pub.string:numericFormat service by providing a decimal value for the input parameter 'num' fails with following error: [ISS.0086.9250] Parameter [num] is not of type: [Integer]

This issue is now resolved.

Integration Server supports string constraints in Swagger document.

Integration Server supports to add string field constraints such as MinLength, MaxLength, and Pattern to the Swagger document generated for REST V2 resources. Integration Server generates the constraints along with the Swagger document that are set as part of the fields in the referred definition or service.

This is a new feature.

Integration Server rolls back the messages to Universal Messaging if message processing fails with a decoding error.

While processing a message using webMethods messaging trigger that receives documents from Universal Messaging, if Integration Server encounters any decoding errors, Integration Server rolls back the message to the message provider (in this case, Universal Messaging).

As the decoding errors are non-transient, the same message rolls back each time Integration Server starts processing that message.

This issue is now resolved. If a webMethods messaging trigger encounters a decoding exception while processing a message, Integration Server acknowledges the message to messaging provider.

The message text for [ISS.0153.0089C] has also changed to "Trigger <trigger_name> failed because of message decoding exception: <exception_message>. Message has been acknowledged to messaging provider."

Passing an empty string as an input in pub.string:tokenize service fails with an error.

In the pub.string:tokenize service when an empty string is passed as an input for the "inString" parameter, Integration Server throws the following error:

com.wm.app.b2b.server.ServiceException: [ISS.0086.9272] inString cannot be empty when empty string is passed as an input for parameter "inString".

This issue is now resolved. Now, pub.string:tokenize service accept emptry string as an input parameter.

After applying a fix that includes PIE-36402 or migrating to a version of Integration Server that includes PIE-36402, execution of a web services that use multi-level document type references exhibits a performance degradation in Integration Server as compared to older releases.

Web services that contain multiple levels of document type references (in which a document reference field includes a field that is a document reference field which in turn also includes a field that is a document reference field, and so forth) exhibit a decrease in performance. This issue is observed after applying a fix containing PIE-36402 (IS_9.8_Core_Fix2) on Integration Sever 9.8 or in Integration Server versions 9.9 and higher.

The performance degradation has been remedied by identifying and removing performance bottlenecks.

An enabled webMethods messaging trigger does not have a registered listener on Universal Messaging but the trigger cannot be restarted.

In some situations, a webMethods messaging trigger that receives messages from Universal Messaging does not create the associated listener on the Universal Messaging server as part of trigger startup. Without the listener, the trigger will not receive messages from Universal Messaging. Even though there is not a listener for the trigger, the trigger remains in an enabled state which prevents Integration Server from restarting the trigger.

This issue is observed in the following scenarios:

This can occur for a variety of reasons, but it most often occurs when the trigger request to create the listener times out or when the Universal Messaging connection alias and the trigger are connecting to different realms.

To resolve the scenarios in which a listener is not created on Universal Messaging as part of startup of the webMethods messaging trigger, Integration Server now attempts to restart any webMethods messaging trigger that is enabled, associated with an active Universal Messaging connection alias, and does not have a registered listener on Universal Messaging server.

Assertion errors related to Adapter Connections are logged when releasing the connection or making the connection available. This happens when the parent service has set a timeout in the flow services.

This issue is now resolved.

Error copying an existing connection as the default values for the connection properties are not copied.

The issue is now resolved.