Using Parametrized Templates of the My webMethods Server Configuration Files
Different installations require setting specific properties in the configuration files for My webMethods Server. You can modify a configuration file to include placeholder values for various server properties and use that file as a template for multiple installations, then supply the values specific to an instance or cluster for My webMethods Server to pick up during container startup.
You supply parametrized templates of the instance or cluster configuration files by mapping a volume to the
instance_cfg or
cluster_cfg directories. When starting new containers, you supply the values specific to the instance or cluster as environment variables or as system properties. For more information about supplying configuration files from a volume, see
Modifying the Configuration of a Container.
My webMethods Server containers accept parametrized values as environment variables passed from the Docker CLI or as system properties specified in the custom_wrapper.conf file for the server instance. In a template file the two types are distinguished using a dedicated prefix, which is env for use with the Docker CLI or sys for system properties in the custom_wrapper.conf file.
My webMethods Server containers accept parametrized values for the following configuration files:
webapp-runtime-config/global-runtime-webapp-config.xml webapp-runtime-config/template-runtime-webapp-config.xml db.xml mws.db.xml defaultPortletAppWeb.xml email.properties healthCheck.json jetty.xml ntlmv2.properties portal.properties searchConfig.properties websso.properties portal.war/WEB-INF/web.xml My webMethods Server containers accept parametrized values for the following properties in the cluster.xml configuration file:
frontEndUrl - the front end URL that you want to configure for the
My webMethods Server cluster.