About the Optimized My webMethods Server Container Startup
When initializing inside a container My webMethods Server uses a mechanism for automatic optimization of the container startup time. The optimization mechanism triggers when the average estimated average execution time of each SQL statement, required for initializing the instance exceeds 20 milliseconds due to network latency between My webMethods Server and the production database. The mechanism uses an in-memory instance of the Derby database, and executes all initial bootstrap activities against that Derby instance. Subsequently, all required data is transferred to the production database. This mechanism applies automatically for all containers that are estimated to execute their startup queries for a longer time than the specified threshold, regardless of the type of the production database.
You can control the SQL execution time threshold at which My webMethods Server triggers the startup optimization, or whether the optimization mechanism triggers at all using the following additional JVM properties:
mws.inmemory.init: controls whether a
My webMethods Server container uses the startup optimisation mechanism. By default, the property is not present in the
custom_wrapper.conf file, and
My webMethods Server executes a sample set of database queries, and initializes using the optimization mechanism only if the average execution time per query exceeds 20 milliseconds. Set to
true to always use the optimization mechanism, or to
false to initialize using the production database, regardless of the SQL execution time.
sql.delay.threshold: the maximum average estimated amount of time for which an SQL query can execute during initialization for
My webMethods Server to start up without using the optimization algorithm. Applies when the
mws.inmemory.init property is not set to true or false. The default value is
20 milliseconds.
Supply the required properties as custom JVM parameters in a
custom_wrapper.conf file from a mapped volume, For more information, see
Modifying the Configuration of a Container.
Note:
Unless you switch off the startup optimization mechanism, all My webMethods Server containers require a local Derby database instance for optimized startup. The Derby scripts are available in the My webMethods Server installation, in Software AG_directory/MWS/server/derby-scripts.zip. When creating custom images from a My webMethods Server installation, make sure that the folder is not skipped, for example by a .dockerignore file that you are using.