Service Development 10.15 | Added, Removed, Deprecated, or Changed Items | Release 10.11
 
Release 10.11
Added Items
*gRPC support Designer can create gRPC descriptors from gRPC service definitions. Developers can then implement the flow services that correspond to the gRPC methods. gRPC clients can invoke these services remotely.
*OpenAPI-based consumer REST API descriptor Users can create a consumer REST API descriptor using an OpenAPI document that conforms to the OpenAPI 3.0.x specification.
*Azul Java 11 runtime support for Designer Service Development Designer Service Development now uses the Azul Java 11 runtime environment instead of Java 1.8.
*Smart mapping The feature predicts the possible mappings between the input and output of a pipeline for a flow service and displays the mappings categorized as 'Very likely', 'Medium likely' and 'Little likely'.
*User interface to view deployable assets and include or exclude assets during deployment. While deploying Integration Server assets to a target environment, Designer displays the deployable assets that include the existing and deleted assets in the environment. Users can choose to retain or remove an asset from the deployment.
*New Java wrapper types for Object and Object List parameters. Designer now supports the 'java.math.BigInteger' and 'java.math.BigDecimal' Java wrapper types for the Object and Object List parameters.
Removed Items
*UDDI support in Designer CentraSite, which is the default UDDI registry for Designer does not support UDDI v2 or v3 now. Hence, service development using UDDI registry is not possible and the UDDI-related functionalities are removed from Designer.
Changed Items
*Universal Messaging client window size for serial webMethods messaging trigger For a serial webMethods messaging trigger that receives documents from Universal Messaging, the corresponding client window size is now set to 1 to ensure serial processing order. Previously, Integration Server did not set the client window size for a serial webMethods messaging trigger. Instead, the serial trigger relied on the default value set in Universal Messaging, which is 100.