This release readme provides information on the release highlights, usage notes, and known issues for the webMethods Cloud Container 3.0 release.
|New features and enhancements||Description|
|Support for B2B and EDI packages in webMethods Cloud Container||webMethods.io B2B and EDI packages are enabled in webMethods Cloud Container to address on-premises migration use-cases. If you are using the on-premises Trading Networks software, you can migrate your existing integration logic involving flows services, mappings or transformations, and document references to cloud using webMethods Cloud Container.|
|Support for grouped packages in webMethods Cloud Container||webMethods Cloud Container provides grouping of packages that has dependencies when defining a solution in webMethods Cloud Container.
|Messaging as a Service||webMethods Cloud Container messaging solution allows you to implement the publish/subscribe messaging styles by bringing the JMS-based messaging capabilities. Messaging is not available by default for a tenant. To enable this functionality, contact Software AG Global Support.|
|Support Two-Way SSL in Messaging as a Service||webMethods Cloud Container now supports Two-Way SSL for Messaging connections. You can store client certificates, associate a certificate with a user account, and set the Two-Way SSL security mode while configuring an SSL connection.|
|Custom Domain||A custom domain is a unique name that identifies your website. There are scenarios where you do not want to expose the default domain provided by webMethods Cloud Container. In such cases, you can customize the default tenant URL or domain and access the tenant using your own domain. Use custom domains if you want to make your application accessible on your own domain. Contact Software AG Global Support for details on how to enable and configure the custom domain capability.|
|SAML 2.0 based Single Sign-On (SSO)||webMethods Cloud Container now supports Single Sign-On (SSO) that allows users to authenticate themselves against an Identity Provider (IdP). Both Service Provider and Identity Provider initiated SSO capabilities are supported.|
|Support to connect to individual Integration Server node in Cluster||In a cluster solution, you can now select an individual webMethods Integration Server node from the Select Integration Server drop-down list. The drop-down has the capability to show up four instances.|
|Support configuration of 4 nodes in IS Cluster on webMethods Cloud Container||In the earlier release, webMethods Cloud Container allowed only three nodes to be created. Now webMethods Cloud Container supports four nodes in an Integration Server cluster solution.|
|Support access to various logs via UI in webMethods Cloud Container||webMethods Cloud Container now supports a new Logs page that gives you an access to download various logs of Integration Server and Universal Messaging within the webMethods Cloud Container.|
|Support for Business Rules on webMethods Cloud Container||You can now select Business Rules when creating a new solution by selecting the WmBusinessRules package in webMethods Cloud Container. Business Rules assets are individual rule projects, created in Rules Development Perspective in Designer.
|Support for 10.7 version||webMethods Cloud Container now supports version 10.7 of Integration Server and Universal Messaging along with existing version 10.5.|
|Support for native configuration deployment||webMethods Cloud Container now supports building assets and configurations using webMethod Asset Build Environement (ABE) without using webMethods Command Central. This would support all the Integration Server packages, Integration Server configuration and Universal Messaging assets.|
|Documentation enhancement||You can now provide feedback on a page, specific content on a page, or on the webMethods Cloud Container documentation website by using the Feedback form.|
|Deprecated||Product version 10.3 is deprecated in this release, so you will not be able to create or update solutions based on v10.3. v10.3 solutions can be upgraded to either v10.5 or v10.7.|
This section provides any additional information you need to work with the v3.0 release of webMethods Cloud Container.
Information on major releases, hotfixes, and patch releases including the latest statistics on cloud system availability, system performance, and security are available on the Cloud Trust Center.
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 or Mozilla Firefox or 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.
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.