How Is Microservices Runtime Different from Integration Server?
Microservices Runtime is a superset of Integration Server which means that Microservices Runtime provides features and functionality that Integration Server does not. However, in addition to these features, Microservices Runtime differs from Integration Server in the following ways:
Microservices Runtime does not support running multiple instances of
Microservices Runtime on the same host machine under the same
Software AG_directory . As such, the
Microservices Runtime directory structure does not include the following directories:
Integration Server_directory /instances/instanceName
When reviewing documentation, references to Integration Server_directory /instances/instanceName for Integration Server map to the Integration Server_directory directory in Microservices Runtime.
Microservices Runtime does not use the OSGi platform. Consequently, a
Microservices Runtime installation does not include the following directory:
Integration Server_directory /profiles/
Microservices Runtime does not use the
Java Service Wrapper developed by
Tanuki Software, Ltd., Consequently,
Microservices Runtime does not use the
Java Service Wrapper configuration files wrapper.conf and custom_wrapper.conf for property settings. Instead, Java system properties are set in
Integration Server_directory /bin/setenv.bat(sh) using the JAVA_CUSTOM_OPTS property.
A JMX port is not enabled by default for
Microservices Runtime.
Microservices Runtime cannot be run as a Windows service.
Note:
The information above applies to a Microservices Runtime only. That is, the information does not apply to an Integration Server equipped with a Microservices Runtime license.