Usage Notes
This section provides any additional information you need to work with the current release of this product.
Beginning with the 10.7 release, webMethods Integration Agent is no longer available. Use webMethods Microservices Runtime instead.
As of Microservices Runtime version 10.4, Microservices Runtime receives runtime configuration settings, such as the Java heap size, from setenv.bat/sh. This change is due to the removal of the OSGI platform from Microservices Runtime.
Command Central cannot be used with Microservices Runtime because Microservices Runtime no longer includes the OSGi.
Additionally, because Microservices Runtime does not support running multiple instances on the same host machine under the same Software AG_directory, the Microservices Runtime directory structure no longer includes the following directories:
Integration Server_directory/instances/instanceName
If you need to modify the default property settings for Microservices Runtime, edit the Integration Server_directory\setenv.bat(sh) file. The following table shows the settings formerly set in the custom_wrapper.conf file that are now set using the setenv.bat/sh file:
wrapper.java.additional.203=-Dwatt.server.append.classes= | | APPENDCLASSES |
wrapper.java.additional.n | | JAVA_CUSTOM_OPTS |
wrapper.java.additional.n=XX:MaxDirectMemorySize= | | JAVA_CUSTOM_OPTS |
wrapper.java.maxmemory | | JAVA_MAX_MEM |
wrapper.java.initmemory | | JAVA_MIN_MEM |
wrapper.java.additional.202=-Dwatt.server.prepend.classes= | | PREPENDCLASSES. |
The following table shows settings you can change that were formerly in the wrapper.conf, custom_wrapper.conf, but are now located in other files or removed
Running Microservices Runtime in Debug Mode | Integration Server_directory\bin\ startDebugMode.bat(sh) |
Java location | JAVA_DIR property in Integration Server_directory\bin\setenv.bat(sh) |
JMX_ENABLED | Integration Server_directory\bin\setenv.bat(sh) |
JMX_PORT | Integration Server_directory\bin\setenv.bat(sh) |
Additionally, the following files are now located in Integration Server_directory\bin:
jcode.bat(sh)startDebugMode.bat(sh)server.bat(sh)startup.bat(sh)shutdown.bat(sh)
As of Microservices Runtime version 10.3, Microservices Runtime creates two predefined URL aliases named “health” and “metrics” which correspond to the health gauge and metrics gathering capabilities respectively. Software AG does not recommend editing the predefined “health” or “metrics” URL aliases.
If you migrate to Microservices Runtime version 10.3 or higher from an earlier version and you already have a URL alias named “health” and/or “metrics”, Microservices Runtime does not create a health and/or metrics URL alias. Any invocations of the health or metrics endpoints will not result in execution of health indicators or metrics gathering, respectively. If you want to use the health gauge and/or metrics gathering, you need to rename your existing health URL alias. Microservices Runtime will create a new health and/or metrics URL alias that corresponds to the health endpoint and/or metrics functionality upon restart.