New configuration variable properties A configuration variables template now includes configuration variables for properties in health indicators, Universal Messaging connection aliases for native messaging, user accounts, and Consul Registry Server aliases.

Prometheus metrics for packages, service request duration, and CloudStreams connectors The Microservices Runtime metrics endpoint returns new metrics for the number of packages, services, and CloudStreams connectors. The endpoint also returns metrics about service request durations.

Microservices Runtime no longer uses OSGi platform No replacement.

Microservices Runtime no longer uses the Java Service Wrapper or the configuration files wrapper.conf and custom_wrapper.conf for property settings. Set Java system properties are set in Integration Server_directory/bin/setenv.bat(sh) using the JAVA_CUSTOM_OPTS property.

Microservices Runtime cannot be run as a Windows service. An Integration Server equipped with a Microservices Runtime license can be run as a Windows service.

Microservices Runtime cannot be used with Digital Event Services. An Integration Server equipped with a Microservices Runtime license can be used with Digital Event Services.

Microservices Runtime cannot be used with the Event Routing feature. An Integration Server equipped with a Microservices Runtime license can be used with the Event Routing feature.

Microservices Runtime cannot be used with Command Central. An Integration Server equipped with a Microservices Runtime license can be used with Command Central.

Microservices Runtime directory structure Because Microservices Runtime no longer uses the OSGi platform, a Microservices Runtime installation does not include the following directory: Integration Server_directory/profiles

Windows Start Menu Commands When running Microservices Runtime on Windows, the Windows start menu commands no longer include the instanceName. Microservices Runtime does not support running multiple instances on the same host machine under the same Software AG_directory.

A JMX port is no longer enabled by default for Microservices Runtime Manually enable the JMX port by editing the IntegrationServer_directory/bin/setenv.bat(sh) file.