Release 10.11

This release readme provides information on the release highlights, usage notes, and known issues for the webMethods Cloud Container 10.11 release.


New features and enhancements Description
Asset Explorer to support different views Asset Explorer now provides you with two layout options to view packages in solutions, namely the List view and Card view. The default view is the Card view, which allows you to see the packages in solutions as blocks.
Connect to a specific cluster node for design-time connection In a clustered solution, the Asset Explorer by default connects to the first node of the webMethods Integration Server instance. If the first instance of the webMethods Integration Server node fails, the Asset Explorer displays the package components for the next available node. Further, if you change the Integration Server instance node on the Administration page, the Asset Explorer displays the assets available for the newly assigned node.
Support for webMethods products version 10.11 for Cloud Container webMethods Cloud Container now supports version 10.11 of Integration Server, Universal Messaging, and BigMemory Max, along with the existing 10.5 and 10.7 versions.

Usage Notes

This section provides any additional information you need to work with the v10.11 release of webMethods Cloud Container.

Known Issues

This section lists the issues for this release that were known when this readme was published.

When an environment is created using the Allow users of Another Environment option, then the users of another environment will not be able to connect using Software AG Designer to the newly created environment using the same user credentials.
Workaround: Create a local user in the linked environment and then proceed.

In webMethods Adapter for JDBC, polling notifications are not retaining the enabled state after the webMethods Cloud Container solution gets Reactivated or Upgraded or Cloned.
Workaround: Enable the Adapter for JDBC polling notifications manually, once the webMethods Integration Server is up and running.

In an Integration Server cluster setup, one of the instances is restarted manually from the user interface. In such circumstances, the runtime transaction may fail a maximum of up to a half-minute because the instance is going down.
Workaround: There is no workaround currently for this issue.

When a Trading Networks service is executed in webMethods Cloud Container, few nodes such as ‘ValidationSvc’, ‘VerificationSvc’, ‘SigningSvc’, ‘Attributes’, ‘PipelineMatchIData’, ‘docType’, ‘dtd’, ‘queries’, ‘qryEvals’, ‘sig_queries’, ‘attribQueries’, ‘envelopeIData’, ‘ValidationSchema’, ‘recordBlueprint’, ‘VERSION_NO’, ‘_contentType’, ‘standard’, ‘version’, ‘transaction’, ‘iidQuery’, ‘EDIBDT.Standard’, ‘EDIBDT.Version’, ‘EDIBDT.DocType’, ‘EDIBDT.IsRootEnv’, ‘EDIBDT.Queries’, ‘EDIBDT.IID’ in the pipeline are not shown in service output rendered in webMethods Cloud Container user interface.
Workaround: There is no workaround currently for this issue.

A global variable of the password type is displayed as encrypted text in Designer.
During variable substitution in flow services, a password configured as a global variable is displayed as encrypted text instead of masked characters (*). This happens when Integration Server configuration containing global variables is deployed using Command Central.
Workaround: The workaround for this issue is to deploy global variables using ACDL files through Deployer.