Integration Server 11.1 | Microservices Runtime Guide | Microservices Runtime vs Integration Server | Microservices Runtime vs Integration Server Feature Comparison
 
Microservices Runtime vs Integration Server Feature Comparison
Microservices Runtime is a superset of Integration Server. In general, this means that Microservices Runtime includes features that are not part of a standard Integration Server. However, some of the features available on a standard Integration Server are not installed by default on Microservices Runtime and must be selected specifically during the installation of Microservices Runtime. Additionally, because Microservices Runtime is optimized for running in a Docker container, Microservices Runtime does not include all of the behavior available on an Integration Server, such as running multiple instances on the same host machine or the use of Command Central. However an Integration Server equipped with a Microservices license provides all of the functionality of Integration Server and Microservices Runtime without the size and speed optimizations made for a Microservices Runtime.
Note:
License keys do not apply to IBM webMethods products version 11.1 GA. License keys may be introduced in a subsequent fix or release. Features enabled due to the removal of the license key and the license key restrictions, are not supported by Microservices Runtime or Integration Server, respectively and are expected to be disabled once licensing is re-enabled via a fix or future release. Refer to the Microservices Runtime vs Integration Server feature comparison below for more details on the differences between the product offerings.
The following table compares features and functionality available across Integration Server, Integration Server equipped with Microservices license, and Microservices Runtime.
Feature
Integration Server
Integration Server with a Microservices license
Microservices Runtime
Integration Server - Core functionality
Yes
Yes
Yes
Command Central support
Yes
Yes
No
Common Directory Services Support
Yes
Yes
Optional
Java Service Wrapper developed by Tanuki Software, Ltd.
Yes
Yes
No
Multi-instance support
Yes
Yes
No
Running as a Windows service
Yes
Yes
No
External RDMS support
Yes
Yes
Optional
WmParquet package
Yes
Yes
No
Circuit breaker support
No
Yes
Yes
Configuration variables support
No
Yes
Yes
Health check endpoint
No
Yes
Yes
Metrics endpoint with metrics in Prometheus format
No
Yes
Yes
CloudStreams
Yes
Yes
Yes
Deployer
Yes
Yes
Yes
Trading Networks
Yes
Yes
Yes
Note:
When building a Docker image for a Microservices Runtime the web service functionality can be excluded. This reduces the size of Docker image. Any web service descriptors that reside on the Microservices Runtime will not execute. Additionally, attempts to execute any of the following web service related built-in services result in a ServiceException:
*pub.soap* services
*pub.utils.ws.setCompatibilityModeFalse
*pub.client:soapClient
*pub.client:soapHTTP
*pub.client:soapRPC
*pub.trigger:createJMSTrigger, when jmsTriggerType=SOAPJMS
For information about excluding web services from a Docker image created for Microservices Runtime, see webMethods Integration Server Administrator's Guide .