The Integration Server log contains the active Session ID even though masking of Session IDs is enabled.

The Integration Server server log contains the active Session ID when the maskSession ID is set to “true” and logging level is set to “Trace”. The active Session ID is mentioned even though masking of Session IDs is enabled.

This issue is now resolved.

Moving or renaming folders containing flow services results in broken references.

When a folder containing a flow service is moved or renamed, any document references present in the flow service are not correctly updated. This results in the flow service containing broken references.

The issue is now resolved.

Designer does not honor the protocol buffer encoding type for a publishable document type created in an earlier version of Integration Server.

When using Designer 9.10 or higher to view or edit a publishable document type created on an Integration Server version 9.10 or earlier, Designer may display the IData as the Encoding type even though the assigned encoding type is protocol buffers. Additionally, if the Encoding type is changed to Protocol buffers, Designer reverts the Encoding type to IData upon save.

This issue is now resolved.

Java services that reference Ehcache classes directly cannot be compiled.

This issue is resolved.

Issues with configuring a restV2 resource.

When configuring a restV2 resource, Integration Server does not display any error on specifying a URL format containing only dynamic parameters for a REST resource. This is incorrect because a URL format must include at least one static parameter.

Integration Server throws an exception on specifying a URL format with only dynamic parameters.

From Command Central, Integration Server instance creation using a YAML template and specifying the dbtype in lower case prevents any update to Audit Logging Destination.

When using Command Central to create an Integration Server instance using a YAML template and specifying the dbtype in lowercase prevents any attempt to change the Audit Logging Destination to 'Database' for an Audit Logger in the Edit Session Logger Details page (Settings> Logging> Edit Session Logger Details).

Additionally, the following error occurs on changing the Session Logger:

RESTART is required due to inability to update in Integration Server.

This issue is resolved. Now, the dbtype is case insensitive in the YAML template, allowing the choice of "Database" as the destination when the ISCoreAudit Functional Pool is set to a valid JDBC pool.

When using Command Central to create an Integration Server instance using a YAML template, specifying the dbtype in lower case causes the functional description to be unavailable.

When creating an Integration Server instance with Command Central, using YAML template and specifying the dbtype in lowercase causes the functional description of functional alias to be unavailable for viewing or editing on the Settings >JDBC Pools > Functional Definitions page.

This issue is resolved. Now, the dbtype is case insensitive in the YAML template and hence, the function description appears correctly.

Unable to add IPv6 address in Integration Server to access a port.

While updating the IP access of a port in the Integration Server Administrator on the Security > Ports > IP Access screen, Integration Server does not allow a user to add an Ipv6 address in the allow/deny lists of IP address.

This issue is now resolved. Integration Server now allows an IPv6 address in the allow/deny lists.

Searching for Integration Server elements results in a NullPointerException.

Searching for Integration Server elements using the Service Development perspective of Designer in a package for which the manifest.v3 file has the system_package attribute missing results in a NullPointerException.

This issue is now resolved.

Executing the is_container script with the createLeanDockerfile option creates a Docker image that does not include the WmCloud package.

This issue is now resolved.

When using a stand-alone Java client created for Integration Server, the client ignores client certificates when establishing an outbound HTTP connection using JSSE.

When a stand-alone Java client uses the Integration Server method com.wm.app.b2b.client.BaseContext.setSSLCertficates() to provide client certificates for the purpose of establishing an SSL connection using JSSE, the client did not provide the destination HTTP server with the client certificates needed to establish the connection.

This issue is now resolved.

Java service compilation fails with an error if the service uses the Common Directory Services API.

If a Java service uses the Common Directory Service API, compilation of the Java service fails with the following error:

class file for com.webmethods.sc.LocalizedException not found

This issue is now resolved.

Integration Server now supports migration when source and target version are same.

The migration utility can now be used for migration where the source and target versions of Integration Server are the same. This can be useful for data center or machine moves.

Unable to change the logging level for Integration Server by using composite templates in Command Central.

When using a composite template in Command Central to change the logging level for an Integration Server, Command Central throws a ConfigurationValidationException and the logging level does not change.

This issue is now resolved.

The Integration Server migration utility does not migrate the quiesce port settings.

This issue is now resolved.

In webMethods Adapter Runtime 10.1, when you create an adapter connection, the Pool Increment Size value in connection management property cannot be greater than Maximum Pool Size value.

This issue is resolved. Pool Increment Size is now validated with Maximum Pool Size value.

In webMethods Adapter Runtime 10.1, the connection pool reset does not happen when adapter connection exception occurs in the design time while creating or configuring the adapter services.

This issue is now resolved.

In webMethods Adapter Runtime 10.1, when you navigate to the Connections screen from the About screen, the left navigation pane of the Connections screen still shows the information related to About screen.

This issue is now resolved.