My webMethods Server 10.15 | My webMethods Server Webhelp | Administering My webMethods Server | Startup and Configuration | Modifying Configuration Files | Configuring JVM Settings for My webMethods Server | Additional JVM Parameters | Configuring Optimized Startup for On-premises Installations
 
Configuring Optimized Startup for On-premises Installations
When starting up in a container, My webMethods Server uses an optimization mechanism to reduce startup time. The optimization mechanism launches an in-memory instance of the Derby database to bootstrap My webMethods Server, then transfers the data to the production database, avoiding most of the network latency overhead. By default, on-premises My webMethods Server installations do not use optimized start mechanism, but you can switch it on by adding the following JVM property to the custom_wrapper.conf file:
Parameter
Description
mws.inmemory.init
Boolean. Whether to use the database query optimization mechanism during start up. The default value is false. Set to true, to enable optimized startup.