Release 2.5.0
This release readme provides information on the release highlights, usage notes, and known issues for the IBM webMethods Cloud Container 2.5 release.
Highlights
No subtopics in thissection
| New features and enhancements | Description |
|---|---|
| Support debugging assets on Cloud Container | IBM webMethods Cloud Container allows you to connect your on-premises Designer under a new perspective called Cloud Service Development (available in Designer 10.5_Fix6 and above) to the Integration Server(s) running in a container as part of the solution landscape. |
| Capability to mock services | Cloud Container now supports mocks when other supporting services that a service may require to properly execute, may not be available when a test case or a test suite is developed or executed. |
| Capability to assert exceptions | You can now create test cases that can assert error messages returned by a service. |
| Capability to generate tests | You can now quickly generate a test from service run results. A successful run result generates a test which asserts the pipeline, and a result with error generates a test which asserts the exception. |
| Asset Explorer for Unit Test | You can now view and access lists of all test suites and test cases for Integration Server assets using the Unit Test Asset Explorer. |
| Support for modifying the clustering details of the solutions) | You can now modify an existing solution’s clustering details. |
| Support for JSON document type from a JSON schema | Cloud Container now supports JSON document type created from JSON schema. You can view the JSON document type properties from the JSON schema section of the properties view. |
| Notify Integration Server restart before promoting assets | Cloud Container now has the provision to notify users about the potential need to restart Integration Server before promoting assets from one environment to another. |
| WebSphere MQ Adapter support | WebSphere MQ Adapter enables Cloud Container solutions to connect and exchange information with IBM WebSphere MQ message queue, and with other systems which uses WebSphere MQ message queuing as their information interface. |