Release 10.12

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

Highlights

New features and enhancements	Description
Support for Microsoft Azure infrastructure provider	In this release, webMethods Cloud Container has been certified to run on Azure cloud platform.
Support new type of solution with only Universal Messaging	webMethods Cloud Container offers the ability to create a new type of solution with only Universal Messaging that allows you to expose a Universal Messaging server without the need to have an Integration Server(s) to the external world. This capability will allow you to publish and consume messages from external applications, such as webMethods.io Integration.
Unit Test enhancements	The following enhancements are now available in the Unit Test framework for Test Case editor screens: You can specify the field that you want to assert instead of the entire output, when assigning values to pipeline variables. Handle empty field validation: If you do not provide an input value for a string field, the string field will not be included in the service invocation. Now you can handle empty values with the help of Include empty values for string types field. If this field is selected, the empty field will be considered. If you do not select this field, the value for the empty field will be derived from the global variable, if defined.
Support for logging framework in Cloud Container	webMethods Cloud Container now supports downloading Integration Server custom logs.

Usage Notes

This section provides any additional information you need to work with webMethods Cloud Container.

Information on major releases, hotfixes, and patch releases including the latest statistics on cloud system availability and planned maintenance events are available on the webMethods.io iPaaS Service Status page.
Software AG Cloud products are available in several geographical regions, operated by different infrastructure providers. Go to the Software AG Cloud Regions website for information on the available products and also the underlying infrastructure provider in each region. See the Tenant URL and Software AG Cloud Region section for more information.
See the Supported Browsers section in the System Requirements for Software AG Products document available on the Software AG Documentation website at https://documentation.softwareag.com for information on the supported browsers.
webMethods Cloud Container is best experienced using Google Chrome browser, Mozilla Firefox, and Microsoft Edge browser. Some features may not work if you are using Microsoft Internet Explorer 10.0 or 11.0 versions.
After a webMethods Cloud Container upgrade, cache and cookies for the older version of the browser are not cleared automatically. This may lead to incorrect display of page content. Ensure that you clear the cache manually after every upgrade, and then log in to webMethods Cloud Container.
Payload restriction in pub-sub calls
In the current configuration where the size of the disk file of Universal Messaging pod is 5GB with the spindle size value set to 3000, it is observed that you can execute the Universal Messaging pub-sub calls with 200KB of payload with a single thread at a time and in a sleep time of 1 second between each message call. Changing these parameters might impact the long-running of the pub-sub scenario. A bigger payload can be handled operationally.

Known Issues

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

SCI-2012
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.

PIEAR-1446
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.

KUB-5326
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.

BOC-12117
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.

PIE-68895
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.

Fixes

This section provides information on the fixes for webMethods Cloud Container v10.12.

Issue ID	Release Date	Region	Description
CLDP-4138	August 27, 2022	US1 Oregon AWS EU2 Frankfurt AWS AU2 Sydney AWS US2 East Azure EU3 West Azure AU1 Australia East Azure	Instead of using the intended time frames of 10 minutes for normal alert intervals and 12 hours for repeating the same alert, the user interface deceives the user into believing that alerts will be issued according to the frequency indicated in the UI. As a result, the disabled check-box field for the alert mail configuration is also eliminated, along with the interval field. This information is made clear in the tool-tip message for the email field.
KUB-15813	August 10, 2022	US1 Oregon AWS EU2 Frankfurt AWS AU2 Sydney AWS US2 East Azure EU3 West Azure AU1 Australia East Azure	When an email address is changed in the alert configurations from the Monitoring page of webMethods Cloud Container, the Alertmanager pod did not get updated, therefore notifications were sent to the old email address. Now the tenant API has implementations to update the Alertmanager secrets.


CSOWAS-10311	August 17, 2022	US1 Oregon AWS EU2 Frankfurt AWS AU2 Sydney AWS US2 East Azure EU3 West Azure AU1 Australia East Azure	Integration Server’s Lucene monitor produced out of memory issues, forcing multiple restarts of the Integration Server cluster. The Integration Server JVM crashed as a result. The issue is now resolved.