Release 11.0.1

What's New

Product Rebranding

webMethods Cloud Container has been renamed to IBM webMethods Cloud Container.

Supported Integration Server Versions

As part of the IBM webMethods Cloud Container 11.0.1 release, Integration Server versions 10.11 and 10.15 are supported.

Deprecation notification

• The support for Business Rules in the Cloud Container has been deprecated and will no longer be available.

• From this release, Product version 10.7 is deprecated. This means that you cannot create or copy solutions using v10.7. It is recommended to use the supported versions (10.11 or 10.15) of IBM webMethods Cloud Container runtimes for deployment of on-premise assets.

Customer Actions

Security Fix Update

A security fix has been implemented as part of the latest Integration Server updates. Apply the recent fixes at your earliest convenience.

Usage Notes

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

• Use the most recent fixes in IBM webMethods Cloud Container to receive the latest updates, including security improvements and new functionalities.

• Information on major releases, hotfixes, and patch releases including the latest statistics on cloud system availability and planned maintenance events are available on the Service Status page.

• Cloud products are available in several geographical regions, operated by different infrastructure providers. Go to the Regions website for information on the available products, IP addresses, and also the underlying infrastructure provider in each region.
  See the Tenant URL and Regions section for more information.

• IBM 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 IBM 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 IBM 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 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 IBM 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 IBM 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 IBM 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.

PIE-83798
Convert pub.cache IData keys to an immutable string.

After upgrading Cloud Container from 10.11 to the latest fix, version 10.15, if an IData object was used as the key when placing a value in cache using a pub.cache service, later attempts to retrieve the value using the same key might fail. This occurs because IData objects are mutable.

To address this issue, Integration Server now includes the server configuration parameter watt.server.cache.iDataKey.toString that specifies whether a com.wm.data.IData object used as a key in one of the pub.cache services is converted to an immutable String before accessing the cache. Set to true to convert an IData object used as a key to a String. Set to false to keep the key as an IData object. The default value is true.

Integration Server does not need to be restarted for changes to this parameter to take effect.

Fixes

This section provides information on the fixes for IBM webMethods Cloud Container v11.0.

Release 11.0.1

Release 11.0